IBM x3250 m4 Server
IBM x3250 m4 Server
System x3250 M4
Type 2583
System x3250 M4
Type 2583
Note
Before using this information and the product it supports, read the general information in
Appendix D, Getting help and technical assistance, on page 519, Notices on page 523, the
Warranty Information document, and the Safety Information and Environmental Notices and User Guide
documents on the IBM Documentation CD.
Contents
Safety . . . . . . . . . . . . . . . vii
Guidelines for trained service technicians . . . . ix
Inspecting for unsafe conditions . . . . . . ix
Guidelines for servicing electrical equipment . . x
Safety statements . . . . . . . . . . . . xi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
. 3
. 3
. 4
. 5
. 6
. 9
. 12
. 13
. 14
. 14
. 16
. 17
. 17
. 18
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
on
.
.
.
.
.
.
.
.
.
.
.
.
.
21
22
22
23
25
25
26
28
29
30
31
32
33
34
35
38
39
40
40
41
42
43
44
45
46
47
49
51
53
54
56
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
58
61
63
63
64
65
66
68
69
70
72
72
73
73
73
74
74
74
78
80
80
81
81
82
83
84
84
85
86
87
87
87
87
88
88
89
89
89
90
92
Chapter 4. Troubleshooting . . . . . . 97
Start here . . . . . . . . . . . . . . . 97
Diagnosing a problem . . . . . . . . . . 97
Undocumented problems . . . . . . . . . 99
Service bulletins . . . . . . . . . . . . 100
iii
Checkout procedure . . . . . . . . . . .
About the checkout procedure. . . . . . .
Performing the checkout procedure . . . . .
Diagnostic tools . . . . . . . . . . . .
Error LEDs . . . . . . . . . . . . .
Power-supply LEDs . . . . . . . . . .
System pulse LEDs . . . . . . . . . .
Event logs . . . . . . . . . . . . .
Viewing event logs through the Setup utility
Viewing event logs without restarting the
server . . . . . . . . . . . . . .
Clearing the event logs . . . . . . . .
POST . . . . . . . . . . . . . . .
IBM Dynamic System Analysis . . . . . .
DSA editions . . . . . . . . . . .
Running DSA Preboot diagnostic programs
Diagnostic text messages . . . . . . .
Viewing the test log results and transferring
the DSA collection . . . . . . . . . .
Automated service request (call home) . . . . .
IBM Electronic Service Agent . . . . . . .
Error messages . . . . . . . . . . . . .
Troubleshooting by symptom . . . . . . . .
General problems . . . . . . . . . . .
Hard disk drive problems . . . . . . . .
DVD drive problems . . . . . . . . . .
Intermittent problems . . . . . . . . .
Keyboard, mouse, or USB-device problems . .
Memory problems . . . . . . . . . . .
Microprocessor problems . . . . . . . .
Monitor problems . . . . . . . . . . .
Network connection problems . . . . . . .
Optional-device problems . . . . . . . .
Power problems . . . . . . . . . . .
Serial port problems . . . . . . . . . .
ServerGuide problems . . . . . . . . .
Software problems. . . . . . . . . . .
Universal Serial Bus (USB) port problems . . .
Solving power problems. . . . . . . . . .
Solving Ethernet controller problems . . . . .
Solving undetermined problems . . . . . . .
Problem determination tips. . . . . . . . .
Recovering the server firmware (UEFI update
failure) . . . . . . . . . . . . . . .
In-band manual recovery method . . . . .
In-band automated boot recovery method . . .
Out-of-band method . . . . . . . . . .
Automated boot recovery (ABR) . . . . . . .
Nx-boot failure . . . . . . . . . . . . .
100
100
101
102
104
106
108
109
110
110
111
112
112
113
114
115
115
115
116
116
116
117
117
120
121
121
122
123
123
126
126
127
128
129
130
131
131
132
133
134
135
135
137
137
137
138
.
.
.
.
.
.
.
.
.
.
. 139
. 144
iv
.
.
.
. 147
. 147
. 148
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
148
149
150
151
152
153
154
155
156
157
160
161
164
165
167
168
170
172
175
176
177
178
180
181
183
185
187
188
190
191
192
. 193
. 194
. 195
. 196
. 197
. 203
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
204
206
206
208
210
212
214
215
217
219
222
223
225
. 230
369
Notices . . . . . . . . . . . . . . 523
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
383
392
400
401
404
407
409
411
416
417
420
490
493
499
503
513
519
520
520
520
521
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 521
. 521
. 521
Trademarks . . . . . . . . . . . . . .
Important notes . . . . . . . . . . . .
Particulate contamination . . . . . . . . .
Documentation format . . . . . . . . . .
Telecommunication regulatory statement . . . .
Electronic emission notices . . . . . . . . .
Federal Communications Commission (FCC)
statement. . . . . . . . . . . . . .
Industry Canada Class A emission compliance
statement. . . . . . . . . . . . . .
Avis de conformit la rglementation
d'Industrie Canada . . . . . . . . . .
Australia and New Zealand Class A statement
European Union EMC Directive conformance
statement. . . . . . . . . . . . . .
Germany Class A statement . . . . . . .
Japan VCCI Class A statement. . . . . . .
Japan Electronics and Information Technology
Industries Association (JEITA) statement . . .
Korea Communications Commission (KCC)
statement. . . . . . . . . . . . . .
Russia Electromagnetic Interference (EMI) Class
A statement . . . . . . . . . . . . .
People's Republic of China Class A electronic
emission statement . . . . . . . . . .
Taiwan Class A compliance statement . . . .
524
524
525
526
526
527
527
527
527
527
528
528
529
530
530
530
530
531
Index . . . . . . . . . . . . . . . 533
Contents
vi
Safety
Before installing this product, read the Safety Information.
vii
viii
Safety
ix
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:
xi
Statement 2
CAUTION:
When replacing the lithium battery, use only IBM Part Number 33F8354 or an
equivalent type battery recommended by the manufacturer. If your system has a
module containing a lithium battery, replace it only with the same module type
made by the same manufacturer. The battery contains lithium and can explode if
not properly used, handled, or disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100C (212F)
v Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Statement 3
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable parts
inside the device.
v Use of controls or adjustments or performance of procedures other than those
specified herein might result in hazardous radiation exposure.
xii
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser diode.
Note the following.
Laser radiation when open. Do not stare into the beam, do not view directly
with optical instruments, and avoid direct exposure to the beam.
Statement 4
CAUTION:
Use safe practices when lifting.
18 kg (39.7 lb)
32 kg (70.5 lb)
55 kg (121.2 lb)
Statement 5
CAUTION:
The power control button on the device and the power switch on the power
supply do not turn off the electrical current supplied to the device. The device
also might have more than one power cord. To remove all electrical current from
the device, ensure that all power cords are disconnected from the power source.
2
1
Safety
xiii
Statement 6
CAUTION:
If you install a strain-relief bracket option over the end of the power cord that is
connected to the device, you must connect the other end of the power cord to an
easily accessible power source.
Statement 8
CAUTION:
Never remove the cover on a power supply or any part that has the following
label attached.
Hazardous voltage, current, and energy levels are present inside any component
that has this label attached. There are no serviceable parts inside these
components. If you suspect a problem with one of these parts, contact a service
technician.
Statement 11
CAUTION:
The following label indicates sharp edges, corners, or joints nearby.
Statement 12
xiv
CAUTION:
The following label indicates a hot surface nearby.
Statement 13
DANGER
Overloading a branch circuit is potentially a fire hazard and a shock hazard
under certain conditions. To avoid these hazards, ensure that your system
electrical requirements do not exceed branch circuit protection requirements.
Refer to the information that is provided with your device for electrical
specifications.
Statement 15
CAUTION:
Make sure that the rack is secured properly to avoid tipping when the server
unit is extended.
Statement 17
CAUTION:
The following label indicates moving parts nearby.
Statement 26
Safety
xv
CAUTION:
Do not place any object on top of rack-mounted devices.
Statement 27
CAUTION:
Hazardous moving parts are nearby.
xvi
1. Racks are measured in vertical increments of 4.45 cm (1.75 inches) each. Each increment is called a "U." A 1-U-high device is 1.75
inches tall
Copyright IBM Corp. 2014
Product name
Machine type
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
In addition, the system service label, which is on the cover of the server, provides a
QR code for mobile access to service information. You can scan the QR code using
a QR code reader and scanner with a mobile device and get quick access to the
IBM Service Information website. The IBM Service Information website provides
additional information for parts installation and replacement videos, and error
codes for server support.
The following illustration shows the QR code (ibm.co/1bdLt6K):
Figure 2. QR code
You can download the 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.
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 System x Documentation CD. It
contains translated environmental notices.
v IBM License Agreement for Machine Code
This document is in PDF on the IBM System x Documentation CD. It provides
translated versions of the IBM License Agreement for Machine Code for your server.
v IBM Warranty Information
This document is in printed format and comes with the server. It contains
warranty terms and a pointer to the IBM Statement of Limited Warranty on the
IBM website.
v Licenses and Attributions Document
This document is in PDF on the IBM System x Documentation CD. It provides the
open source notices.
v Rack Installation Instructions
This printed document contains instructions for installing the server in a rack.
v Safety Information
This document is in PDF on the IBM System x 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.
Depending on the server model, additional documentation might be included on
the IBM System x Documentation CD.
The System x and BladeCenter Tools Center is an online information center that
contains information about tools for updating, managing, and deploying firmware,
device drivers, and operating systems. The System x and BladeCenter Tools Center
is at http://www.ibm.com/support/entry/portal/docdisplay?lndocid=TOOLCENTER.
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 updated
documentation and technical updates, go to http://www.ibm.com/supportportal.
Memory:
Integrated functions:
v Matrox G200
v ServeRAID-BR10il v2 SAS/SATA
adapter that provides RAID levels
0, 1, and 10
Environment:
v Air temperature:
Server on: 10C to 35C (50.0F
to 95.0F); altitude: 0 to 914.4 m
(3000 ft)
Server on: 10C to 32C (50.0F
to 89.6F); altitude: 914.4 m
(3000 ft) to 2133.6 m (7000 ft)
v Width:
439 mm (17.28 inches) (without
rack brackets)
478 mm (18.82 inches) (with
rack brackets)
v Maximum weight: 10.67 kg (23.53
lb) depending on your
configuration
Electrical input:
v Particulate contamination:
Attention: Airborne particulates
and reactive gases acting alone or
in combination with other
environmental factors such as
humidity or temperature might
pose a risk to the server. For
information about the limits for
particulates and gases, see
Particulate contamination.
v Humidity:
Note:
10
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 460-watt hot-swap power supplies and 5
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
460-watt hot-swap power supply and four fans. You can order the second
optional power supply for power redundancy.
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
IMM2 is used with the systems-management software that comes with the
server, you can manage the functions of the server locally and remotely. The
IMM2 also provides system monitoring, event recording, and network alert
capability. The systems-management connector on the rear of the server is
dedicated to the IMM2. The dedicated systems-management connector provides
additional security by physically separating the management network traffic
from the production network. You can use the Setup utility to configure the
server to use a dedicated systems-management network or a shared network.
v UEFI-compliant server firmware
The UEFI firmware offers several features, including Unified Extensible
Firmware Interface (UEFI) version 2.1 compliance, Active Energy Management
(AEM) technology, enhanced reliability, availability, and serviceability (RAS)
capabilities, and basic input/output system (BIOS) compatibility support. UEFI
replaces the BIOS and defines a standard interface between the operating
system, platform firmware, and external devices. The server is capable of
booting UEFI-compliant operating systems, BIOS-based operating systems, and
BIOS-based adapters as well as UEFI-compliant adapters. For more information
about UEFI-compliant firmware, go to http://www.ibm.com/support/entry/
portal/docdisplay?lndocid=MIGR-5083207.
Note: The server does not support DOS (Disk Operating System).
11
12
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
System health
Updates
Event notification
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
source of the problems
Chapter 1. The IBM System x3250 M4 Type 2583 server
13
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 IBM Systems Director
Information Center at http://publib.boulder.ibm.com/infocenter/director/v6r1x/
index.jsp?topic=/director_6.1/fqm0_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.
Front view
The following illustration shows the controls, LEDs, and connectors on the front of
the server.
Note: The illustrations in this document might differ slightly from your hardware.
The following illustration shows the controls, LEDs, and connectors on the front of
the two 3.5-inch simple-swap hard disk drive model.
Reset button
Power-control button
Power-on LED
The following illustration shows the controls, LEDs, and connectors on the front of
the four 2.5-inch simple-swap hard disk drive model.
14
Reset button
Power-control button
Power-on LED
The following illustration shows the controls, LEDs, and connectors on the front of
the four 2.5-inch hot-swap hard disk drive model.
Reset button
Power-control button
Power-on LED
15
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 DVD drive is in use.
v Hot-swap hard disk drive activity LEDs (some models):
This LED is used on 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 Hot-swap hard disk drive status LEDs (some models):
This LED is used on 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.
Rear view
The following illustrations show the connectors and LEDs on the rear of the server.
Note: The illustrations in this document might differ slightly from your hardware.
The following illustration shows the LEDs and connectors on the rear of the fixed
power-supply model.
Ethernet 1 Ethernet 1 Ethernet 2
activity LED link LED
link LED
Ethernet 2
Serial
activity LED
connector
Power-cord
connector
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 1
The following illustration shows the LEDs and connectors on the rear of the
redundant power-supply model.
Ethernet 1 Ethernet 1 Ethernet 2
activity LED link LED
link LED
Ethernet 2
Serial
activity LED
connector
Power-cord
connector
AC
AC
DC
DC
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 1
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.
16
v Ethernet activity LEDs: When these LEDs are lit, they indicate that there is
activity between the server and the network.
v AC power LED: This green LED provides status information about the power
supply. During typical operation, both the ac and dc power LEDs are lit. For any
other combination of LEDs, see Power-supply LEDs on page 106.
v DC power LED: This green LED provides status information about the power
supply. During typical operation, both the ac and dc power LEDs are lit. For any
other combination of LEDs, see Power-supply LEDs on page 106.
v Power supply error LED: When this yellow LED is lit, it indicates that the
power supply has failed.
v Power cord connector: Connect the power cord to this connector.
v Video connector: Connect a monitor to this connector.
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, keyboard, or
other device to any of these connectors.
v Ethernet connectors: Use either of these connectors to connect the server to a
network. When you use the Ethernet 1 connector, the network can be shared
with the IMM2 through a single network cable.
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.
Procedure
1. Press the power-on button to turn on the server.
2. The server can also be turned on in any of the following ways:
17
v If a power failure occurs while the server is turned on, the server will restart
automatically when power is restored.
v If your operating system supports the Wake on LAN feature, the Wake on
LAN feature can turn on the server.
Note: When 4 GB or more of memory (physical or logical) is installed, some
memory is reserved for various system resources and is unavailable to the
operating system. The amount of memory that is reserved for system resources
depends on the operating system, the configuration of the server, and the
configured PCI options.
CAUTION:
The power control button on the device 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
Procedure
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.
18
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 assembly and the
PCI-X 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.
19
20
Procedure
1. Make sure that the server and the installed firmware levels support the devices
that you are installing. If necessary, update the UEFI and IMM2 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
69. 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 Firmware Update Guides
document, go to http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5082923. Additional hints and tips are available
from the following website:
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 DSA Preboot diagnostic programs on page 114 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.
21
Procedure
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: http://www.ecurep.ibm.com/
app/upload_hw
22
Server components
The following illustration shows the major components in the server.
The following illustration shows the major components in the server. The
illustrations in this document might differ slightly from your hardware.
Model with fixed power supply:
Cover
ServeRAID - BR10il
v2 adapter ( some
models )
Heat sink
Air baffle
Microprocessor
DIMM
System board
Operator information
panel assembly
Front bezel
3.5-inch simple-swap
hard disk drive
(some models)
23
Cover
ServeRAID - BR10il
v2 adapter ( some
models )
Heat sink
Air baffle
Microprocessor
DIMM
System board
Hot-swap
power supply
Fans
Operator information
panel assembly
Front bezel
2.5-inch hot-swap
hard disk drive
backplane
(some models)
2.5-inch hot-swap
hard disk drive
(some models)
Paddle card
Safety 240VA cover
Blue on a component indicates touch points, where you can grip the component to
remove it from or install it in the server, open or close a latch, and so on.
Orange on a component or an orange label on or near a component indicates that
the component can be hot-swapped, which means that if the server and operating
system support hot-swap capability, you can remove or install the component
while the server is running.
Note: 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.
24
Power 2
SAS backplane
configuration
connector
Power 1
SATA 5
Operator information
panel connector
DIMM 2
DIMM 1
Microprocessor
SATA 3
DIMM 4
DIMM 3
SATA 4
Battery
Fan 4 connector
Fan 3 connector
DIMM 1
DIMM 2
Fan 1 connector
Fan 2 connector
SATA 2
SATA 1
SATA 0
DIMM 4
DIMM 3
25
Ethernet connector 1/
USB connectors 1&2
Ethernet connector 2/
USB connectors 3&4
Video
DIMM 2
DIMM 1
Microprocessor
Serial (COM1)
DIMM 4
DIMM 3
NMI button
26
DIMM 4
Low security
jumper (J P 19)
DIMM 3
DIMM 2
DIMM 1
TPM physical
presence
jumper (JP 10)
ME recovery
jumper (JP 8)
Clear CMOS
jumper (JP 1)
ME flash override
jumper (JP 9)
TPM initialization
jumper (JP 11)
Microprocessor
Figure 5. Location of the switches, jumpers, and buttons on the system board. (cy1cd021a)
Jumper name
Jumper setting
JP1
JP2
JP8
ME recovery jumper
JP9
JP10
Trusted Platform Module (TPM) physical Pins 1 and 2: Enable TPM physical
presence jumper
presence (default)
Pins 2 and 3: Disable TPM physical
presence
JP11
27
Jumper name
Jumper setting
JP12
JP19
Note:
1. If no jumper is present, the server responds as if the pins are set to 1 and 2.
2. Changing the position of the boot block jumper from pins 1 and 2 to pins 2 and 3 before the server is turned on
alters which flash ROM page is loaded. Do not change the jumper pin position after the server is turned on. This
can cause an unpredictable problem.
System-board LEDs
The following illustration shows the light-emitting diodes (LEDs) on the system
board.
System board
error LED
Standby power
LED
Microprocessor
DIMM 2
DIMM 1
RTMM
Hearbeat LED
DIMM 4
DIMM 3
Microprocessor
error LED
DIMM 1 - 4
error LEDs
IMM2 hearbeat
LED
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 and LEDs inside
the server on the system board
Table 3. System-board LEDs
LED
28
Description
29
30
DIMMs
installed in each
channel
DIMM type
Ranks per
DIMM (any
combination)
DIMM speed
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
v The following table lists the maximum DIMM population using ranked
UDIMMs.
Table 5. Maximum memory population using ranked UDIMMs (depending on your model)
Number of
UDIMMs
DIMM type
Single-rank UDIMMs 1 GB
4 GB
Dual-rank UDIMMs
2 GB
8 GB
Dual-rank UDIMMs
4 GB
16 GB
Size
Total memory
31
DIMM type
Size
Total memory
Dual-rank UDIMMs
8 GB
32 GB
v The following table shows the UDIMM memory population rule to optimize the
system performance.
Table 6. UDIMM population rule
DIMM connector 1
DIMM connector 2
DIMM connector 3
DIMM connector 4
Populated
Empty
Empty
Empty
Populated
Empty
Populated
Empty
Populated
Populated
Populated
Populated
Installing drives
This section describes the rules to install 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 fixed power supply models can support up to four 2.5-inch or 3.5-inch
hot-swap or simple-swap hard disk drives.
v The redundant power supply models can support up to eight 2.5-inch hot-swap
or simple-swap 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
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us.
32
Hard disk
drive assembly
Filler panel
v To install a 2.5-inch simple-swap hard disk drive, slide the drive into the
server until the drive clicks into the server and connects to the backplate.
SATA hard disk
drive back plate
Hard disk
drive assembly
Filler panel
6. Insert the filler panel into the bay to cover the drive.
33
Release latch
Activity LED
(green)
Error LED
(yellow)
2.5-inch hot-swap
hard disk drive
Drive handle
34
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.
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
Note: You might have to reconfigure the disk arrays after you install hard disk
drives. See the RAID documentation on the IBM ServeRAID Support CD for
information about RAID controllers.
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.
35
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.
Release tab
36
6. Touch the static-protective package that contains the new DVD drive to any
unpainted metal surface on the server; then, remove the DVD 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. Remove the retention clip from the DVD drive filler.
9. Attach the drive retention clip (that comes with the DVD drive filler) to the
side of the new DVD drive.
Drive retention clip
Alignment pins
10. Align the drive in the drive bay and slide the drive into the DVD drive bay
until the drive clicks into place.
37
Installation guidelines
Use the installation guidelines to install the IBM System x3250 M4 Type 2583.
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 and the guidelines in
Working inside the server with the power on on page 40, and Handling
static-sensitive devices on page 40. 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://www.ibm.com/support/entry/portal/docdisplay?lndocid=TOOLCENTER
v Before you install optional hardware, make sure that the server is working
correctly. Start the server, and make sure that the operating system starts, if an
operating system is installed, or that a 19990305 error code is displayed,
indicating that an operating system was not found but the server is otherwise
working correctly. If the server is not working correctly, see Running DSA
Preboot diagnostic programs on page 114 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.
38
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.
39
40
Procedure
1. Read the safety information that begins in the begin of this documentation.
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, loosen the two thumbscrews on the
front of the server and remove the server out of the rack enclosure; then, place
it on a flat, static-protective surface.
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 front panel, on the rear panel, and
LEDs inside the server on the system board, then, see this documentation for
information about how to solve the problem.
4. Press down firmly on the blue tab on the top of the cover (on the right side
near the front of the server) and slide the cover toward the rear of the server
until the cover has disengaged from the chassis.
41
Cover-release
button
Procedure
1. Read the safety information that begins in the begin of this documentation.
2. Turn off the server and peripheral devices and disconnect the power cords and
all external cables, if necessary.
3. Remove the cover (see Removing the cover on page 41).
4. Grasp the air baffle; then, lift it up out of the server and set it aside.
42
Air baffle
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.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. If an adapter is installed in the PCI riser-card assembly, disconnect any cables
that are connected to the adapter.
3. Grasp the front and rear of the PCI riser-card assembly and lift it out of the PCI
riser-card slot on the system board.
43
Riser-card
assembly
4. Disconnect any cables from the adapters in the PCI riser-card assembly.
5. Place the PCI riser-card assembly on a flat, static-protective surface. If you are
instructed to return the PCI riser-card assembly, follow all packaging
instructions, and use any packaging materials for shipping that are supplied to
you.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Position the fan so that the airflow arrow on the fan points toward the rear of
the server.
Note: The correct airflow is from the front to the rear of the server.
44
Fan bracket
cable channel
Fan
Fan bracket
Fan bracket
cable slot
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
Installing drives
This section describes the rules to install 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.
45
v The fixed power supply models can support up to four 2.5-inch or 3.5-inch
hot-swap or simple-swap hard disk drives.
v The redundant power supply models can support up to eight 2.5-inch hot-swap
or simple-swap 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
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us.
Procedure
1. Remove the filler panel from the empty drive bay. Keep the filler panel in a
safe place.
2. Touch the static-protective package that contains the drive to any unpainted
metal surface on the server; then, remove the drive from the package and place
it on a static-protective surface.
3. Install 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.
46
Hard disk
drive assembly
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.
4. If you are installing additional hot-swap hard disk drives, do so now.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
Procedure
1. Remove the filler panel from the empty drive bay.
Chapter 2. Installing optional devices
47
2. Touch the static-protective package that contains the drive to any unpainted
metal surface on the server; then, remove the drive from the package and place
it on a static-protective surface.
3. Install the hard disk drive in the 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.
Hard disk
drive assembly
Filler panel
Hard disk
drive assembly
Filler panel
b. Gently push the drive into the bay until the drive stops.
4. Reinstall the drive bay filler panel that you removed earlier.
5. If you are installing additional simple-swap hard disk drives, do so now.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
48
Procedure
1. 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
2. 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
49
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable
parts inside the device.
v Use of controls or adjustments or performance of procedures other than
those specified herein might result in hazardous radiation exposure.
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser
diode. Note the following.
Laser radiation when open. Do not stare into the beam, do not view
directly with optical instruments, and avoid direct exposure to the beam.
Alignment pins
6. 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.
50
7. Follow the instructions that come with the drive to set any jumpers or switches.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
51
4R = quad-rank
is the device organization or bit width (for example, x4, x8, or x16)
x4 = x4 organization (4 DQ lines per SDRAM)
x8 = x8 organization
x16 = x16 organization
wwwww is the DIMM bandwidth, in MBps
v 8500 = 8.53 GBps (DDR3-1066 SDRAMs, 8-byte primary data bus)
v 10600 = 10.66 GBps (DDR3-1333 SDRAMs, 8-byte primary data bus)
v
- m
v
v
v
52
DIMMs
installed in each
channel
DIMM type
Ranks per
DIMM (any
combination)
DIMM speed
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
v The following table lists the maximum DIMM population using ranked
UDIMMs.
Table 8. Maximum memory population using ranked UDIMMs (depending on your model)
Number of
UDIMMs
DIMM type
Single-rank UDIMMs 1 GB
4 GB
Dual-rank UDIMMs
2 GB
8 GB
Dual-rank UDIMMs
4 GB
16 GB
Dual-rank UDIMMs
8 GB
32 GB
Size
Total memory
v The following table shows the UDIMM memory population rule to optimize the
system performance.
Table 9. UDIMM population rule
DIMM connector 1
DIMM connector 2
DIMM connector 3
DIMM connector 4
Populated
Empty
Empty
Empty
Populated
Empty
Populated
Empty
Populated
Populated
Populated
Populated
53
Installing a DIMM
Use this information to install a DIMM.
DIMM 4
DIMM 3
DIMM 2
DIMM 1
Microprocessor
DIMM 4
DIMM 3
The following illustration shows the location of the DIMM connectors on the
system board.
DIMM 2
DIMM 1
Figure 17. The location of the DIMM connectors on the system board. (jinhu114)
Procedure
1. Locate the DIMM connectors on the system board. Determine the connectors
into which you will install the DIMMs. Install the DIMMs in the sequence
shown in the following table.
54
1, 3
2, 4
3. 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.
4. Turn the DIMM so that the alignment slot align correctly with the alignment
tab.
5. Insert the DIMM into the connector by aligning the edges of the DIMM with
the slots at the ends of the DIMM connector.
6. 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.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
55
Installing an adapter
Use this information to install an adapter.
Procedure
1. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
56
2. Touch the static-protective package that contains the adapter to any unpainted
metal surface on the server; then, remove the adapter from the package.
3. Place the adapter, component side up, on a flat, static-protective surface and set
any jumpers or switches as described by the adapter manufacturer, if necessary.
4. Follow the cabling instructions, if any come with the adapter. Route the adapter
cables before you install the adapter.
5. Remove the expansion-slot cover from the PCI riser-card assembly and save for
future use.
6. Align the connector on the adapter with the connector on the PCI riser-card
assembly, then, insert the adapter into the PCI riser-card assembly. Press the
edge of the connector firmly into the PCI riser-card assembly. Make sure that
the adapter is securely installed in the PCI riser-card assembly.
Important: Make sure that the U-shaped opening in the metal adapter bracket
engages the tab on the expansion-slot bracket.
Adapter
bracket
Adapter
Expansion-slot
bracket
Tab
7. Install the PCI riser-card assembly (see Replacing the PCI riser-card assembly
on page 63).
Attention: When you install an adapter, make sure that the adapter is
correctly seated in the PCI riser-card assembly and that the PCI riser-card
assembly is securely seated in the riser-card connector on the system board
before you turn on the server. An incorrectly seated adapter might cause
damage to the system board, the PCI riser-card assembly, or the adapter.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
Note: If the server is configured for RAID operation through an optional
ServeRAID adapter, you might have to reconfigure your disk arrays after you
install an adapter. See the ServeRAID documentation on the IBM ServerRAID
Support CD for additional information about RAID operation and complete
instructions for using ServeRAID Manager.
57
Procedure
1. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
2. Remove the expansion-slot cover on the slot that you intend to use and save
for future use.
Attention: PCI expansion-slot covers must be installed on all vacant slots.
This maintains the electronic emissions standards of the server and ensures
proper ventilation of server components.
Expansion-slot cover
Adapter
Expansion slot 2
Expansion slot 1
Expansion-slot cover
Riser-card
assembly
Adapter
3. Touch the static-protective package that contains the new ServeRAID adapter to
any unpainted surface on the outside of the server; then, grasp the adapter by
the top edge or upper corners of the adapter and remove it from the package.
4. Take the signal cable that is attached to the drive backplane and connect it to
the ServeRAID adapter.
v If you install a ServeRAID adapter in slot 1 on the PCI riser-card assembly,
route the signal cable from the drive backplane as shown in the following
illustration.
58
SAS/SATA
signal cable
59
ServeRAID adapter
SAS/SATA signal
cable
Hard disk
drive backplane
5. Align the ServeRAID adapter so that the keys align correctly with the
connector on the PCI riser-card assembly.
6. Insert the ServeRAID adapter into the connector on the PCI riser-card assembly
until it is firmly seated.
Attention: Incomplete insertion might cause damage to the server or the
adapter.
7. Install the PCI riser-card assembly (see Replacing the PCI riser-card assembly
on page 63).
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
Note: When you restart the server, you are prompted to import the existing RAID
configuration to the new ServeRAID adapter.
60
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
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.
61
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
Procedure
1. Grasp the side clip and pull to remove the power-supply filler panel from the
empty power-supply bay. Save the power-supply filler panel in case you
remove the power supply at a later time.
Important: During normal operation, each power-supply bay must contain
either a power supply or power-supply filler panel for proper cooling.
Power
supply
filler
Power
supply
Power
supply
release tab
2. Slide the hot-swap power supply into the bay until the release latch clicks into
place.
3. Connect one end of the power cord for the new power supply into the ac
connector on the back of the power supply; then, connect the other end of the
power cord into a properly grounded electrical outlet.
4. If the server is turned off, turn on the server.
5. Make sure that the ac power LED on the power supply is lit, indicating that the
power supply is operating correctly. If the server is turned on, make sure that
the dc power LED on the power supply is lit also.
What to do next
If you have other devices to install, do so now. Otherwise, go to Completing the
installation on page 63.
62
Procedure
1. If you removed the PCI riser-card assembly, reinstall it (see Replacing the PCI
riser-card assembly).
2. If you removed the air baffle, reinstall it (see Replacing the air baffle on page
64).
3. If you removed the server cover, replace it (see Replacing the cover on page
65).
4. Install the server in the rack cabinet (see the Rack Installation Instructions that
come with the server for instructions).
5. Reconnect the cables and power cords (see Connecting the cables on page
66).
6. Update the server configuration (see Updating the server configuration on
page 68).
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 22.
Procedure
1. Install the adapters in the PCI riser-card assembly (see Replacing a ServeRAID
adapter on page 161)
2. Reconnect any adapter cables that you disconnected when you removed the
PCI riser-card assembly.
3. Carefully align the PCI riser-card assembly with the guides on the rear of the
server and with the PCI riser-card connector on the system board; then, place
your thumbs on locations marked by the blue tabs and press down on the PCI
riser-card assembly. Make sure that the riser-card assembly is fully seated in the
Chapter 2. Installing optional devices
63
Riser-card
assembly
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Align the air baffle pins with the baffle pin holes on the server chassis and fan
cage assembly; then, lower the air baffle into the server. Press the air baffle
down until it is securely seated.
64
Air baffle
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Attention: For proper cooling and airflow, replace the air baffle before turning on
the server. Operating the server with an air baffle removed might damage server
components.
Procedure
1. Position the cover on top of the server so that approximately 13 mm (0.5 inch)
extends from the rear.
Chapter 2. Installing optional devices
65
3. Make sure that the cover correctly engages all the inset tabs on the server.
4. Install the server into the rack enclosure and tighten the two front thumbscrews
to secure the server in the rack.
5. Reconnect the external cables and power cords.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Reset button
Power-control button
Power-on LED
66
USB 1 connector
USB 2 connector
Power-cord
connector
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 1
The following illustration shows the locations of the input and output connectors
on the rear of the server.
Ethernet 1 Ethernet 1 Ethernet 2
activity LED link LED
link LED
Ethernet 2
Serial
activity LED
connector
Power-cord
connector
PCI slot 1
PCI slot 2
Power-cord
connector
AC
AC
DC
DC
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 1
Procedure
1. You must turn off the server before you connect or disconnect cables.
2. 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.
3. Cable identifiers are printed on the cables that come with the server and
optional devices. Use these identifiers to connect the cables to the correct
connectors.
67
68
69
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.
70
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 IMM2 memory and mapping it to the
server as a virtual drive
The blue-screen capture feature captures the video display contents before the
IMM2 restarts the server when the IMM2 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 83.
v Ethernet controller configuration
For information about configuring the Ethernet controller, see Configuring the
Ethernet controller on page 87.
v IBM Advanced Settings Utility (ASU) program
Use this program as an alternative to the Setup utility for modifying UEFI
settings and IMM2 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 88.
v Configuring RAID arrays
For information about configuring RAID arrays, see Configuring RAID arrays
on page 87.
The following table lists the different server configurations and the applications
that are available for configuring and managing RAID arrays.
Table 11. Server configuration and applications for configuring and managing RAID arrays
RAID array configuration
(before operating system is
installed)
ServeRAID-H1110 adapter
ServeRAID-M1115 adapter
MegaRAID BIOS
Configuration Utility (press
Ctrl+H to start), pre-boot CLI
(press Ctrl+P to start),
ServerGuide, HII
ServeRAID-M5110 adapter
ServeRAID-M5120 adapter
Server configuration
Notes:
71
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.
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 has 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
72
73
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.
74
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
Chapter 3. Configuration information and instructions
75
76
77
v
v
Passwords
From the User Security menu choice, you can set, change, and delete a power-on
password and an administrator password.
The User Security menu 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 must type the power-on 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.
78
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.
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.
v Remove the battery from the server, wait 30 seconds, and then reinstall it.
v Change the position of the power-on password switch (enable switch 2 of the
system board switch block (SW1) to bypass the password check (see
System-board switches and jumpers on page 26 for more information).
Attention: Before you change any switch settings or move any jumpers, turn
off the server; then, disconnect all power cords and external cables. See the
safety information that begins 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 SW1 is Off.
While the server is turned off, move switch 2 of the switch block SW1 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.
79
Procedure
1.
2.
3.
4.
Results
The next time the server starts, it returns to the startup sequence that is set in the
Setup utility.
80
Procedure
1. Turn on the server.
Note: Approximately 20 seconds after the server is connected to AC power, the
power-control button becomes active.
2. When the prompt <F1> Setup is displayed, press F1. If you have set an
administrator password, you must type the administrator password to access
the full Setup utility menu. If you do not type the administrator password, a
limited Setup utility menu is available.
3. Select System Settings > Integrated Management Module, then set Power
Restore Policy setting to Restore.
4. Go back to System Configuration and Boot Management > Save Settings.
5. Go back and check the Power Policy setting to verify that it is set to Restore
(the default).
What to do next
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.
81
v
v
v
v
82
The IMM2 also provides the following remote server management capabilities
through the ipmitool 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 IMM2, see the Integrated Management Module II User's
Guide at http://www.ibm.com/support/entry/portal/docdisplay?lndocid=migr5086346.
83
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).
Procedure
1. Turn off 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. (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.
84
4.
5.
6.
7.
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.
85
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.
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.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/vsphereesxi-vcenter-server-50-installation-setup-guide.pdf.
86
Procedure
1. Turn on the server.
Note: Approximately 10 seconds after the server is connected to power, the
power-control button becomes active.
87
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.
88
Procedure
1. Check for the latest version of IBM Systems Director:
a. Go to http://www.ibm.com/systems/software/director/resources.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.
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.
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 click Continue.
6. Download the available updates.
7. Copy the downloaded files to the management server.
8. On the management server, on the Welcome page of the IBM Systems Director
web interface, click the Manage tab, and click Update Manager.
9. Click Import updates and specify the location of the downloaded files that
you copied to the management server.
10. Return to the Welcome page of the Web interface, and click View updates.
89
11. Select the updates that you want to install, and click Install to start the
installation wizard.
Procedure
1. Download the Advanced Settings Utility (ASU):
a. Go to http://www.ibm.com/supportportal.
Click on the Downloads tab at the top of the panel.
Under ToolsCenter, select View ToolsCenter downloads.
Select Advanced Settings Utility (ASU).
Scroll down and click on the link and download the ASU version for your
operating system.
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)
b.
c.
d.
e.
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:
90
91
Where:
imm_external_ip
The external IMM LAN IP address. There is no default value. This
parameter is required.
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).
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> --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.
5. Restart the server.
Procedure
1. Download the Advanced Settings Utility (ASU):
a. Go to http://www.ibm.com/supportportal.
b. Click on the Downloads tab at the top of the panel.
c. Under ToolsCenter, select View ToolsCenter downloads.
d. Select Advanced Settings Utility (ASU).
e. Scroll down and click on the link and download the ASU version for your
operating system.
2. ASU sets the DMI in the Integrated Management Module (IMM). Select one of
the following methods to access the Integrated Management Module (IMM) to
set the DMI:
92
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
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:
93
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>
--user <imm_user_id> --password <imm_password>
Examples that do use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>
v Online KCS access (unauthenticated and user restricted):
You do not need to specify a value for access_method when you use this
access method.
The KCS access method uses the IPMI/KCS interface. This method requires
that the IPMI driver be installed. Some operating systems have the IPMI
driver installed by default. ASU provides the corresponding mapping layer.
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.
a. Go to http://www.ibm.com/supportportal.
b. Click on the Downloads tab at the top of the panel.
c. Under ToolsCenter, select View ToolsCenter downloads.
d. Select Advanced Settings Utility (ASU).
e. Scroll down and click on the link and download the ASU version for
your operating system. 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
default values and not using the default values:
Examples that do not use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>
v 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
The IMM account (1 of 12 accounts). The default value is USERID.
94
imm_password
The IMM account password (1 of 12 accounts). The default value is
PASSW0RD (with a zero 0 not an O).
The following commands are examples of using the userid and password
default values and not using the default values:
Examples that do not use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> --host <imm_ip>
--user <imm_user_id> --password <imm_password>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> --host <imm_ip>
--user <imm_user_id> --password <imm_password>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> --host <imm_ip>
--user <imm_user_id> --password <imm_password>
Examples that do use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> --host <imm_ip>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> --host <imm_ip>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> --host <imm_ip>
v Bootable media:
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.
5. Restart the server.
95
96
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 519 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 Diagnostic tools on page 102 for
information about using light path diagnostics LEDs.
v Event logs: See Event logs on page 109 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.
Copyright IBM Corp. 2014
97
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
http://www.ibm.com/support/fixcentral.
Attention: Installing the wrong firmware or device-driver update might cause
the server to malfunction. Before you install a firmware or device-driver
update, read any readme and change history files that are provided with the
downloaded update. These files contain important information about the
update and the procedure for installing the update, including any special
procedure for updating from an early firmware or device-driver version to the
latest version.
Important: Some cluster solutions require specific code levels or coordinated
code updates. If the device is part of a cluster solution, verify that the latest
level of code is supported for the cluster solution before you update the code.
a. Install UpdateXpress system updates. You can install code updates that are
packaged as an UpdateXpress System Pack or UpdateXpress CD image. An
UpdateXpress System Pack contains an integration-tested bundle of online
firmware and device-driver updates for your server. In addition, you can
use IBM ToolsCenter Bootable Media Creator to create bootable media that
is suitable for applying firmware updates and running preboot diagnostics.
For more information about UpdateXpress System Packs, see
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERVXPRESS and Updating the firmware on page 69. 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
http://www.ibm.com/support/fixcentral.
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
98
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
99
Service bulletins
IBM continually updates the support website with the latest tips and techniques
that you can use to solve problem that you might have with the IBM System x3250
M4 server.
To find service bulletins that are available for the IBM IBM System x3250 M4
server, go to and search for 2583, and retain.
Checkout procedure
The checkout procedure is the sequence of tasks that you should follow to
diagnose a problem in the server.
100
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 106).
b. Turn off the server and all external devices.
c. Check all internal and external devices for compatibility at
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us.
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 116.
h. Check the system-error LED on the operator information panel. If it is lit,
check the light path diagnostics LEDs (see Diagnostic tools on page 102).
i. Check for the following results:
v Successful completion of POST (see POST on page 112 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
116; if necessary, see Solving undetermined problems on page 133.
v Yes: Run DSA (see Running DSA Preboot diagnostic programs on page
114).
If DSA reports an error, follow the instructions in Appendix C, DSA
diagnostic test results, on page 383.
If DSA does not report an error but you still suspect a problem, see
Solving undetermined problems on page 133.
Chapter 4. Troubleshooting
101
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related
problems.
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 109 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 IMM2 provides advanced service-processor control,
monitoring, and alerting function. If an environmental condition exceeds a
threshold or if a system component fails, the IMM2 lights LEDs to help you
diagnose the problem, records the error in the IMM2 event log, and alerts you to
the problem. Optionally, the IMM2 also provides a virtual presence capability for
remote server management capabilities. The IMM2 provides remote server
management through the following industry-standard interfaces:
Intelligent Platform Management 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 II (IMM2) on page 82, Appendix A,
Integrated Management Module II (IMM2) error messages, on page 229, 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:
-
102
Chapter 4. Troubleshooting
103
Error LEDs
This section describes the Error LEDs on the system board and the suggested
actions to correct the detected problems.
The illustration shows the system-board LEDs. The system board has error LEDs
that will help to locate the source of the error. Run the diagnostic programs to find
out the cause of the error (see IBM Dynamic System Analysis on page 112).
System board
error LED
Standby power
LED
DIMM 2
DIMM 1
Microprocessor
RTMM
Hearbeat LED
DIMM 4
DIMM 3
Microprocessor
error LED
DIMM 1 - 4
error LEDs
IMM2 hearbeat
LED
The server is designed so that LEDs remain lit when the server is connected to an
ac power source but is not turned on, provided that the power supply is operating
correctly. This feature helps you to isolate the problem when the operating system
is shut down.
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 and LEDs inside
the server on the system board.
Many errors are first indicated by a lit system-error LED on the control-panel
assembly of the server. If this LED is lit, one or more LEDs elsewhere in the server
might also be lit and can direct you to the source of the error.
Before you work inside the server to view the LEDs, read the Safety on page vii
and Handling static-sensitive devices on page 40.
If an error occurs, view the server LEDs in the following order:
1. Check the control-panel assembly on the front of the server. If the system-error
LED is lit, it indicates that an error has occurred.
104
2. Check the front and rear of the server to determine whether any component
LEDs are lit.
3. Remove the server top cover and look inside the server for lit LEDs. Certain
components inside the server have LEDs that will be lit to indicate the location
of a problem. For example, a DIMM error will light the LED next to the failing
DIMM on the system board.
4. Look at the system service label inside the top cover of the server, which gives
an overview of internal components. This information can often provide
enough information to correct the error.
The following table describes the LEDs on the system board and suggested actions
to correct the detected problems.
Table 12. The suggested actions to correct the detected problem for each LED light
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.
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.
LED
Description
Action
Chapter 4. Troubleshooting
105
Table 12. The suggested actions to correct the detected problem for each LED light (continued)
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.
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.
LED
Description
Action
Power-supply LEDs
This section describes the power-supply LEDs on the rear of the server and the
suggested actions to correct the detected problems.
The following minimum configuration is required for the server to start:
v One microprocessor
v One 1 GB DIMM
v Power supply
v Power cord
v ServeRAID SAS/SATA adapter
v Four cooling fans
The following illustration shows the LEDs and connectors on the rear of the fixed
power-supply model.
106
Power-cord
connector
PCI slot 1
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
Power-supply
error LED
(amber)
Figure 27. LEDs and connectors on the rear of the fixed power-supply model
The following illustration shows the LEDs and connectors on the rear of the
redundant power-supply model.
Ethernet 1 Ethernet 1 Ethernet 2
activity LED link LED
link LED
Ethernet 2
Serial
activity LED
connector
Power-cord
connector
AC
AC
DC
DC
PCI slot 2
NMI button
AC Power LED
(green)
DC Power LED
(green)
PCI slot 1
Figure 28. LEDs and connectors on the rear of the redundant power-supply model
The following table describes the problems that are indicated by various
combinations of the power-supply LEDs and suggested actions to correct the
detected problems.
Table 13. Power-supply LEDs
AC Power-supply LEDs
AC
DC
Error
Description
Action
Notes
On
On
Off
Normal
operation
Off
Off
Off
This is a normal
condition when no
ac power is present.
Chapter 4. Troubleshooting
107
DC
On
Off
On
Error
Description
Action
Notes
Off
Faulty system
board or faulty
power supply
Off or
Flashing
On
Faulty power
supply
On
On
Off
Normal
operation
On
On
On
Power supply is
faulty but still
operational
Typically indicates
that a power supply
is not fully seated.
This is a normal
2. If the system board error (fault) LED
condition before
is not lit, replace the power supply.
turning on the
3. (Trained technician only) If the system system.
board error LED is lit, replace the
system board.
Description
Action
RTMM heartbeat
IMM2 heartbeat
108
Event logs
Error codes and messages are displayed in POST event log, system-event log,
Integrated Management Module II (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 74). For more
information about POST error codes, see Appendix B, UEFI (POST) error
codes, on page 369.
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 II (IMM2).
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 229.
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 IMM2 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 IMM2, POST, and system management interrupt (SMI)
events. You can view the IMM2 event log through the IMM2 web interface. For
more information, see Logging on to the web interface on page 85. You can
also view the IMM2 event log through the Dynamic System Analysis (DSA)
program (as the ASM event log). For more information about IMM2 error
messages, see Appendix A, Integrated Management Module II (IMM2) error
messages, on page 229.
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 IMM2 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 110).
For more information about DSA and DSA messages, see IBM Dynamic System
Analysis on page 112 and Appendix C, DSA diagnostic test results, on page
383.
Chapter 4. Troubleshooting
109
Procedure
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a
power-on password and an administrator password, you must type the
administrator password to view the event logs.
3. Select System Event Log and use one of the following procedures:
v To view the POST event log, select POST Event Viewer.
v To view the system-event log, select System Event Log.
110
Action
The server is not hung and is not connected to a network v Run DSA Portable to view the diagnostic event log
(using an operating system controlled network ports).
(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 IMM2 to view
the system-event log locally (requires RNDIS USB
LAN driver).
The server is not hung and the Integrated Management
Module II (IMM2) is connected to a network.
Procedure
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a
power-on password and an administrator password, you must type the
administrator password to view the event logs.
3. To clear the IMM2 system-event log, select System Event Log > Clear System
Event Log, then, press Enter twice.
Chapter 4. Troubleshooting
111
POST
When you turn on the server, it performs a series of tests to check the operation of
the server components and some optional devices in the server. This series of tests
is called the power-on self-test, or POST.
Note: This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter (when
you are prompted), for POST to run.
If POST detects a problem, an error message is displayed. See Appendix B, UEFI
(POST) error codes, on page 369 for more information.
If POST detects a problem, an error message is sent to the POST event log, see
Event logs on page 109 for more 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 383.
If you cannot find a problem by using DSA, see Solving undetermined problems
on page 133 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.
112
DSA editions
Two editions of Dynamic System Analysis are available.
v DSA Portable
DSA Portable Edition runs within the operating system; you do not have to
restart the server to run it. It is packaged as a self-extracting file that you
download from the web. When you run the file, it self-extracts to a temporary
folder and performs comprehensive collection of hardware and operating-system
information. After it runs, it automatically deletes the temporary files and folder
and leaves the results of the data collection and diagnostics on the server.
If you are able to start the server, use DSA Portable.
v DSA Preboot
DSA Preboot runs outside of the operating system; you must restart the server to
run it. It is provided in the flash memory on the server, or you can create a
bootable media such as a CD, DVD, ISO, USB, or PXE using the IBM
ToolsCenter Bootable Media Creator (BoMC). For more details, see the BoMC
User Guide at http://www.ibm.com/support/entry/portal/
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 unable 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.
Chapter 4. Troubleshooting
113
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.
114
Viewing the test log results and transferring the DSA collection
Use this information to view the test log results and transferring the DSA
collection.
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.
Chapter 4. Troubleshooting
115
Error messages
This section provides the list of error codes and messages for UEFI/POST, IMM2,
and DSA that are generated when a problem is detected.
See Appendix B, UEFI (POST) error codes, on page 369, Appendix A, Integrated
Management Module II (IMM2) error messages, on page 229, and Appendix C,
DSA diagnostic test results, on page 383 for more information.
Troubleshooting by symptom
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
Procedure
1. Check the system-error LED on the operator information panel; if it is lit, check
the light path diagnostics LEDs (see Diagnostic tools on page 102).
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 383).
4. Reinstall the new software or new device.
116
General problems
Table 16. General symptoms and actions
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.
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
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
screen is on. Cannot start the
Setup utility by pressing F1.
Action
Not all drives are recognized by Remove the drive that is indicated by the diagnostic tests; then, run the hard disk
the hard disk drive diagnostic
drive diagnostic tests again. If the remaining drives are recognized, replace the
tests.
drive that you removed with a new one.
The server stops responding
during the hard disk drive
diagnostic test.
Remove the hard disk drive that was being tested when the server stopped
responding, and run the diagnostic test again. If the hard disk drive diagnostic
test runs successfully, replace the drive that you removed with a new one.
Reseat all hard disk drives and cables; then, run the hard disk drive diagnostic
tests again.
Run the diagnostic SCSI Fixed Disk Test (see Running DSA Preboot diagnostic
programs on page 114).
Note: This test is not available on servers that have RAID arrays or servers that
have SATA hard disk drives.
Chapter 4. Troubleshooting
117
Action
1. Observe the associated yellow hard disk drive status LED. If the LED is lit, it
indicates a drive fault.
2. If the LED is lit, remove the drive from the bay, wait 45 seconds, and reinsert
the drive, making sure that the drive assembly connects to the hard disk
drive backplane.
3. Observe the associated green hard disk drive activity LED and the yellow
status LED:
v If the green activity LED is flashing and the yellow status LED is not lit,
the drive is recognized by the controller and is working correctly. Run the
DSA hard disk drive test to determine whether the drive is detected.
v If the green activity LED is flashing and the yellow status LED is flashing
slowly, the drive is recognized by the controller and is rebuilding.
v If neither LED is lit or flashing, check the hard disk drive backplane (go to
step 4).
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 4.
If the activity of the LEDs changes, return to step 1.
4. Make sure that the hard disk drive backplane is correctly seated. When it is
correctly seated, the drive assemblies correctly connect to the backplane
without bowing or causing movement of the backplane.
5. Reseat the backplane power cable and repeat steps 1 through 3.
6. Reseat the backplane signal cable and repeat steps 1 through 3.
7. Reseat the backplane configuration cable and repeat steps 1 through 3.
8. Suspect the backplane signal cable or the backplane:
v Replace the affected backplane signal cable.
v Replace the affected backplane.
9. Run the DSA tests for the SAS/SATA adapter and hard disk drives (seeIBM
Dynamic System Analysis on page 112 ).
v If the adapter passes the test but the drives are not recognized, replace the
backplane signal cable and run the tests again.
v Replace the backplane.
v If the adapter fails the test, disconnect the backplane signal cable from the
adapter and run the tests again.
v If the adapter fails the test, replace the adapter.
10.
Make sure that the hard disk drive, SAS/SATA RAID adapter, and server device
drivers and firmware are at the latest level.
Important: Some cluster solutions require specific code levels or coordinated code
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.
1. Review the storage subsystem logs for indications of problems within the
storage subsystem, such as backplane or cable problems.
2. See Problem determination tips on page 134.
118
Action
1. Make sure that the hard disk drive is recognized by the adapter (the green
hard disk drive activity LED is flashing).
2. Review the SAS/SATA RAID adapter documentation to determine the correct
configuration parameters and settings.
A green hard disk drive activity 1. If the green hard disk drive activity LED does not flash when the drive is in
LED does not accurately
use, run the DSA disk drive test (see IBM Dynamic System Analysis on page
represent the actual state of the
112).
associated drive. (Hot-swap
2. Use one of the following procedures:
hard disk drives)
v If the drive passes the test, replace the backplane.
v If the drive fails the test, replace the drive.
An yellow hard disk drive
status LED does not accurately
represent the actual state of the
associated drive. (Hot-swap
hard disk drives)
1. If the yellow hard disk drive LED and the RAID adapter software do not
indicate the same status for the drive, complete the following steps:
a. Turn off the server.
b. Reseat the SAS/SATA adapter.
c. Reseat the backplane configuration cable, 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.
2. See Problem determination tips on page 134.
Chapter 4. Troubleshooting
119
Action
120
Intermittent problems
Table 19. Intermittent problems and actions
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.
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
Action
Chapter 4. Troubleshooting
121
Memory problems
Table 21. Memory problems and actions
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.
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 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 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 DSA Preboot diagnostic programs on page 114).
5. Make sure that there is no memory mismatch when the server is at the
minimum memory configuration..
6. Add one pair of DIMMs at a time, making sure that the DIMMs in each pair
match.
7. Reseat the DIMM.
8.
9. Re-enable all DIMMs using the Setup utility, and then restart the server.
10. Replace the following components one at a time, in the order shown,
restarting the server each time:
a. DIMMs
b. (Trained technician only) Replace the system board
Multiple rows of DIMMs in a
branch are identified as failing.
Note: Each time you install or remove a DIMM, you must disconnect the server
from the power source; then, wait 10 seconds before restarting the server.
1. Reseat the DIMMs; then, restart the server.
2. Replace the failing DIMM.
3. (Trained technician only) Replace the system board
122
Microprocessor problems
Table 22. Microprocessor's symptoms and actions
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.
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
1. 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.
2. (Trained technician only) Reseat microprocessor 1
3. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. (Trained technician only) Microprocessor 2
b. (Trained technician only) System board
Monitor 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.
Table 23. Monitor and video's symptoms and actions
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.
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
Chapter 4. Troubleshooting
123
Action
1. If the server is attached to a KVM switch, bypass the KVM switch to eliminate
it as a possible cause of the problem: connect the monitor cable directly to the
correct connector on the rear of the server.
2. Make sure that:
v The server is turned on. If there is no power to the server, see Power
problems on page 127.
v The monitor cables are connected correctly.
v The monitor is turned on and the brightness and contrast controls are
adjusted correctly.
v No POST errors are generated when the server is turned on.
3. Make sure that the correct server is controlling the monitor, if applicable.
4. Make sure that damaged server firmware is not affecting the video; see
Updating the firmware on page 69.
5. Observe the checkpoint LEDs on the system board; if the codes are changing,
go to next step.
6. 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
7. See Solving undetermined problems on page 133.
124
Action
The monitor has screen jitter, or 1. If the monitor self-tests show that the monitor is working correctly, consider
the screen image is wavy,
the location of the monitor. Magnetic fields around other devices (such as
unreadable, rolling, or
transformers, appliances, fluorescents, and other monitors) can cause screen
distorted.
jitter or wavy, unreadable, rolling, or distorted screen images. If this happens,
turn off the monitor.
Attention: Moving a color monitor while it is turned on might cause screen
discoloration.
Move the device and the monitor at least 305 mm (12 in.) apart, and turn on
the monitor.
Notes:
a. To prevent diskette drive read/write errors, make sure that the distance
between the monitor and any external diskette drive is at least 76 mm (3
in.).
b. Non-IBM monitor cables might cause unpredictable problems.
2. Reseat the monitor and cable.
3. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. Monitor
b. (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 69) with the correct language.
2. Reseat the monitor and cable.
3. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. Monitor
b. (Trained technician only) System board
Chapter 4. Troubleshooting
125
Action
Optional-device problems
Table 25. Optional-device problems and actions
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.
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
1. Make sure that all of the cable connections for the device are secure.
2. If the device comes with test instructions, use those instructions to test the
device.
3. Reseat the failing device.
4. Replace the failing device.
126
Power problems
Table 26. Power problems and actions
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.
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
Chapter 4. Troubleshooting
127
Action
Action
128
Action
ServerGuide problems
Table 28. ServerGuide problems and actions
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.
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
1. Make sure that the server supports the ServerGuide program and has a
startable (bootable) DVD drive.
2. If the startup (boot) sequence settings have been changed, make sure that the
DVD drive is first in the startup sequence.
3. If more than one DVD drive is installed, make sure that only one drive is set
as the primary drive. Start the CD from the primary drive.
The operating-system
installation program
continuously loops.
2. Make sure that the SAS hard disk drive cables are securely connected.
Chapter 4. Troubleshooting
129
Action
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
Table 29. Software problems and actions
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.
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
1. To determine whether the problem is caused by the software, make sure that:
v The server has the minimum memory that is needed to use the software. For
memory requirements, see the information that comes with the software. If
you have just installed an adapter or memory, the server might have a
memory-address conflict.
v The software is designed to operate on the server.
v Other software works on the server.
v The software works on another server.
2. If you received any error messages when using the software, see the
information that comes with the software for a description of the messages and
suggested solutions to the problem.
3. Contact the software vendor.
130
Action
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 Diagnostic tools
on page 102).
4. 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 Solving undetermined problems on page
133).
5. 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.
What to do next
If the server does not start from the minimum configuration, see Power-supply
LEDs on page 106 to replace the components in the minimum configuration one
at a time until the problem is isolated.
Chapter 4. Troubleshooting
131
Procedure
1. Make sure that the correct device drivers, which come with the server are
installed and that they are at the latest level.
2. Make sure that the Ethernet cable is installed correctly.
v The cable must be securely attached at all connections. If the cable is
attached but the problem remains, try a different cable.
v If you set the Ethernet controller to operate at 100 Mbps, you must use
Category 5 cabling.
v If you directly connect two servers (without a hub), or if you are not using a
hub with X ports, use a crossover cable. To determine whether a hub has an
X port, check the port label. If the label contains an X, the hub has an X port.
3. 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.
4. 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.
v 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.
v 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.
5. 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.
6. Check for operating-system-specific causes of the problem.
7. Make sure that the device drivers on the client and server are using the same
protocol.
8.
What to do next
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.
132
Procedure
1. Turn off the server.
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.
Note: The minimum configuration required for the server to start is one
microprocessor and one 2 GB DIMM.
4. Turn on the server. If the problem remains, suspect the following components
in the following order:
a. Power supply
b. Memory
c. Microprocessor
d. System board
What to do next
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.
Chapter 4. Troubleshooting
133
ID label
134
See Appendix D, Getting help and technical assistance, on page 519 for
information about calling IBM for service.
Procedure
1. Read the safety information that begins on Safety on page vii and
Installation guidelines on page 38.
2. Turn off the server, and disconnect all power cords and external cables.
3. Unlock and remove the cover (see Removing the cover on page 41).
4. Locate the UEFI boot backup jumper on the system board.
Chapter 4. Troubleshooting
135
DIMM 4
Low security
jumper (J P 19)
DIMM 3
DIMM 2
DIMM 1
TPM physical
presence
jumper (JP 10)
ME recovery
jumper (JP 8)
Clear CMOS
jumper (JP 1)
ME flash override
jumper (JP 9)
TPM initialization
jumper (JP 11)
Microprocessor
Figure 30. Location of the switches, jumpers, and buttons on the system board
5. Move the UEFI boot backup jumper 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 41).
11. Move the UEFI boot backup jumper from pins 2 and 3 back to the primary
position (pins 1 and 2).
12. Reinstall the cover (see Replacing the cover on page 65).
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.
15. Remove cover (see Removing the cover on page 41).
16. Reset the CMOS by removing the system battery (see Removing the system
battery on page 183).
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 185).
19. Reinstall the cover (see Replacing the cover on page 65).
20. Reconnect the power cord and any cables that you removed.
21. Restart the server. The system begins the power-on self-test (POST).
136
22. If these recovery efforts fail, contact your IBM service representative for
support.
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.
3. Restart the server.
4. At the firmware splash screen, press F3 when prompted to restore to the
primary bank. The server boots from the primary bank.
Out-of-band method
See the IMM2 documentation (Integrated Management Module II User's Guide) at
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5086346.
Procedure
1. Restart the server.
2. When the prompt Press F3 to restore to primary is displayed, press F3 to start
the server from the primary bank.
Chapter 4. Troubleshooting
137
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).
138
139
21
4
20
5
19
6
18
17
7
16
15
8
14
13
12
10
11
The following table lists the part numbers for the server replaceable components.
140
Index
CRU part
number (Tier
1)
Description
CRU part
number (Tier
2)
FRU part
number
Top cover
81Y7455
81Y7457
49Y4737
Air baffle
81Y7453
44T1572
44T1574
44T1575
00D4953
00D4957
00D4961
49Y1422
81Y6301
39Y7229
00AL207
81Y7456
90Y5958
81Y7466
46C6757
81Y7465
81Y7464
10
42D0788
10
43W7625
10
39M4517
10
39M4529
11
39M4343
12
81Y7460
12
44T2248
13
49Y2028
13
49Y1992
13
49Y1997
13
42D0678
141
Index
Description
CRU part
number (Tier
1)
CRU part
number (Tier
2)
FRU part
number
13
42D0638
13
42D0708
13
49Y2004
13
81Y9723
13
81Y9727
13
81Y9731
13
90Y8644
13
90Y8649
14
Front bezel
81Y7458
15
16
CD-RW/DVD-RW drive
44W3256
16
DVD-ROM drive
44W3254
17
49Y4868
18
81Y7454
19
System board
00AL958
20
69Y5148
20
69Y5149
20
69Y5151
20
69Y5152
20
81Y6933
20
81Y6945
20
81Y6947
20
81Y6949
20
81Y6951
20
00Y7408
20
81Y7504
20
00D8552
20
00D8552
20
00D8553
20
00D8554
20
00D8555
20
00D8556
142
90Y5298
Index
CRU part
number (Tier
1)
Description
CRU part
number (Tier
2)
FRU part
number
20
00D8557
20
94Y6303
20
99Y1447
21
Heat sink
22
81Y7526
23
00D3712
81Y7495
33F8354
81Y7494
46M0861
46M0918
81Y4494
46M0864
81Y7463
81Y7464
81Y7465
81Y7466
00D4344
59Y3229
00D8685
42C1802
42C1816
42C1822
42C1819
42D0491
42D0500
49Y4821
81Y7528
81Y7461
42D0507
42D0516
49Y7947
49Y7949
94Y6263
90Y9355
90Y9373
49Y4232
49Y4242
Bracket, EAR
39M4351
Miscellaneous kit
81Y7459
Chapter 5. Parts listing, IBM System x3250 M4 Type 2583
143
Index
CRU part
number (Tier
1)
Description
1U tool-less kit
24P1121
Service label
81Y7507
Service label
00D4340
Service label
00D4342
CRU part
number (Tier
2)
FRU part
number
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.
IBM power cord part number
39M5206
China
39M5102
39M5123
144
39M5130
Denmark
39M5144
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
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
39M5199
Japan
39M5068
39M5226
India
39M5233
Brazil
145
146
147
Procedure
1. Read the safety information that begins in the begin of this documentation.
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, loosen the two thumbscrews on the
front of the server and remove the server out of the rack enclosure; then, place
it on a flat, static-protective surface.
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 front panel, on the rear panel, and
LEDs inside the server on the system board, then, see this documentation for
information about how to solve the problem.
4. Press down firmly on the blue tab on the top of the cover (on the right side
near the front of the server) and slide the cover toward the rear of the server
until the cover has disengaged from the chassis.
148
Cover-release
button
Procedure
1. Position the cover on top of the server so that approximately 13 mm (0.5 inch)
extends from the rear.
2. Slide the cover toward the front of the server.
149
3. Make sure that the cover correctly engages all the inset tabs on the server.
4. Install the server into the rack enclosure and tighten the two front thumbscrews
to secure the server in the rack.
5. Reconnect the external cables and power cords.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Procedure
1. If the server has been installed in a rack, press the two release latches on the
front of the server and remove the server out of the rack enclosure.
Attention: Two or more people are required to remove the server from a rack
cabinet.
2. Turn off the server and all peripheral devices, and disconnect the power cords
and all external cables.
3. Remove the server top cover (see Removing the cover on page 41).
150
4. From inside the server, press the bezel release latch toward the left side of the
server.
5. Pivot the bezel forward and pull it away from the server.
Release
latch
Bezel
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Attention: For proper cooling and airflow, replace the bezel and server cover
before you turn on the server.
Procedure
151
Release
latch
Bezel
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Attention: For proper cooling and airflow, replace the bezel and server cover
before you turn on the server.
Procedure
1. Read the safety information that begins in the begin of this documentation.
2. Turn off the server and peripheral devices and disconnect the power cords and
all external cables, if necessary.
3. Remove the cover (see Removing the cover on page 41).
4. Grasp the air baffle; then, lift it up out of the server and set it aside.
152
Air baffle
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.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Align the air baffle pins with the baffle pin holes on the server chassis and fan
cage assembly; then, lower the air baffle into the server. Press the air baffle
down until it is securely seated.
153
Air baffle
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Attention: For proper cooling and airflow, replace the air baffle before turning on
the server. Operating the server with an air baffle removed might damage server
components.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. If an adapter is installed in the PCI riser-card assembly, disconnect any cables
that are connected to the adapter.
154
3. Grasp the front and rear of the PCI riser-card assembly and lift it out of the PCI
riser-card slot on the system board.
Riser-card
assembly
4. Disconnect any cables from the adapters in the PCI riser-card assembly.
5. Place the PCI riser-card assembly on a flat, static-protective surface. If you are
instructed to return the PCI riser-card assembly, follow all packaging
instructions, and use any packaging materials for shipping that are supplied to
you.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Install the adapters in the PCI riser-card assembly (see Replacing a ServeRAID
adapter on page 161)
155
2. Reconnect any adapter cables that you disconnected when you removed the
PCI riser-card assembly.
3. Carefully align the PCI riser-card assembly with the guides on the rear of the
server and with the PCI riser-card connector on the system board; then, place
your thumbs on locations marked by the blue tabs and press down on the PCI
riser-card assembly. Make sure that the riser-card assembly is fully seated in the
connector on the system board.
Riser-card
assembly
Removing an adapter
Use this information to remove an adapter.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
156
Expansion slot 2
Expansion slot 1
Expansion-slot cover
Riser-card
assembly
Adapter
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Replacing an adapter
Use this information to replace an adapter.
157
158
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
3. Touch the static-protective package that contains the adapter to any unpainted
metal surface on the server; then, remove the adapter from the package.
4. Place the adapter, component side up, on a flat, static-protective surface and set
any jumpers or switches as described by the adapter manufacturer, if necessary.
5. Follow the cabling instructions, if any come with the adapter. Route the adapter
cables before you install the adapter.
6. Remove the expansion-slot cover from the PCI riser-card assembly and save for
future use.
7. Align the connector on the adapter with the connector on the PCI riser-card
assembly, then, insert the adapter into the PCI riser-card assembly. Press the
edge of the connector firmly into the PCI riser-card assembly. Make sure that
the adapter is securely installed in the PCI riser-card assembly.
Important: Make sure that the U-shaped opening in the metal adapter bracket
engages the tab on the expansion-slot bracket.
159
Adapter
bracket
Adapter
Expansion-slot
bracket
Tab
8. Install the PCI riser-card assembly (see Replacing the PCI riser-card assembly
on page 63).
Attention: When you install an adapter, make sure that the adapter is
correctly seated in the PCI riser-card assembly and that the PCI riser-card
assembly is securely seated in the riser-card connector on the system board
before you turn on the server. An incorrectly seated adapter might cause
damage to the system board, the PCI riser-card assembly, or the adapter.
9. Reinstall the cover (see Replacing the cover on page 65).
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Note: To support Windows 2011 SBS on Brocade adapters need to use at least
3.0.0.0 driver package or later version.
Procedure
1. Remove the cover (see Removing the cover on page 41).
160
2. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
3. Disconnect the signal cable from the ServeRAID adapter.
4. Grasp the PCI riser-card assembly at the front grip point and rear edges and lift
to remove it from the server.
5. Place the PCI riser-card assembly on a flat, static-protective surface.
6. Carefully grasp the end of the ServeRAID adapter and pull the adapter out of
the connector on the PCI riser-card assembly.
Expansion-slot cover
Adapter
Expansion slot 2
Expansion slot 1
Expansion-slot cover
Riser-card
assembly
Adapter
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Remove the cover (see Removing the cover on page 41).
Chapter 6. Removing and replacing components
161
2. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
3. Remove the expansion-slot cover on the slot that you intend to use and save
for future use.
Attention: PCI expansion-slot covers must be installed on all vacant slots.
This maintains the electronic emissions standards of the server and ensures
proper ventilation of server components.
Expansion-slot cover
Adapter
Expansion slot 2
Expansion slot 1
Expansion-slot cover
Riser-card
assembly
Adapter
4. Touch the static-protective package that contains the new ServeRAID adapter to
any unpainted surface on the outside of the server; then, grasp the adapter by
the top edge or upper corners of the adapter and remove it from the package.
5. Take the signal cable that is attached to the drive backplane and connect it to
the ServeRAID adapter.
v If you install a ServeRAID-BR10il v2 adapter in slot 1 on the PCI riser-card
assembly, route the signal cable from the drive backplane as shown in the
following illustration.
SAS/SATA
signal cable
162
SAS/SATA signal
cable
Hard disk
drive backplane
6. Align the ServeRAID adapter so that the keys align correctly with the
connector on the PCI riser-card assembly.
7. Insert the ServeRAID adapter into the connector on the PCI riser-card assembly
until it is firmly seated.
Attention: Incomplete insertion might cause damage to the server or the
adapter.
8. Install the PCI riser-card assembly (see Replacing the PCI riser-card assembly
on page 63).
9. Reinstall the cover (see Replacing the cover on page 65).
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Note: When you restart the server, you are prompted to import the existing RAID
configuration to the new ServeRAID adapter.
163
Hard disk
drive assembly
Filler panel
v To remove a 2.5-inch simple-swap hard disk drive, press the release latch and
pull the drive out of the bay.
164
Hard disk
drive assembly
Filler panel
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Remove the filler panel from the empty drive bay.
2. Touch the static-protective package that contains the drive to any unpainted
metal surface on the server; then, remove the drive from the package and place
it on a static-protective surface.
Chapter 6. Removing and replacing components
165
Hard disk
drive assembly
Filler panel
b. To install a 2.5-inch simple-swap hard disk drive, slide the drive into the
server until the drive clicks into the server and connects to the backplate.
SATA hard disk
drive back plate
Hard disk
drive assembly
Filler panel
5. Reinstall the drive bay filler panel that you removed earlier.
6. If you are installing additional simple-swap hard disk drives, do so now.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
166
Hard disk
drive assembly
Procedure
1. Move the handle on the drive to the open position (perpendicular to the drive).
2. Slide the release latch gently to the left to unlock the drive handle.
3. Grasp the handle and pull the hot-swap hard disk drive out of the drive bay.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
Chapter 6. Removing and replacing components
167
supplied to you.
Procedure
1. Make sure that the server top cover is in place and fully closed.
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.
168
Hard disk
drive assembly
Filler panel
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
169
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Press the release tab (the rear of the drive-retention clip) toward the drive right
side of the server to release the clip; then, while you press the tab, push the
drive out of the bay.
Note: You might have to push the right-rear corner of the drive toward the
front of the server to move the drive initially.
Release tab
170
Alignment pins
4. If you are not replacing the DVD drive, reinstall the DVD drive filler.
a. Attach the drive-retention clip to the side of the DVD drive filler that you
removed
b. Slide the DVD drive filler into the DVD drive bay until the drive filler clicks
into place.
Attention: To maintain proper system cooling, do not operate the server for
more than 10 minutes without either a drive or filler panel installed in each
bay.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
171
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. 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.
172
Release tab
3. Remove the retention clip from the DVD drive filler panel. Save the DVD drive
filler panel for future use.
4. Attach the drive-retention clip that you removed in the step above to the side
of the new DVD drive
Drive retention clip
Alignment pins
Note: If you are installing an optical drive that contains a laser, observe the
following safety precautions.
Statement 3
173
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable
parts inside the device.
v Use of controls or adjustments or performance of procedures other than
those specified herein might result in hazardous radiation exposure.
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser
diode. Note the following.
Laser radiation when open. Do not stare into the beam, do not view
directly with optical instruments, and avoid direct exposure to the beam.
6. Follow the instructions that come with the drive to set any jumpers or switches.
174
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Removing a DIMM
Use this information to remove a memory module.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. 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, handle the clips gently.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
175
2R = dual-rank
4R = quad-rank
is the device organization or bit width (for example, x4, x8, or x16)
x4 = x4 organization (4 DQ lines per SDRAM)
x8 = x8 organization
176
Note:
1. To determine the type of a DIMM, see the label on the DIMM. The
information on the label is in the format xGB nRxx PC3v-xxxxxx-xx-xx-xx.
The numeral in the sixth numerical position indicates whether the DIMM is
single-rank (n=1) or dual-rank (n=2).
2. 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 70.
DIMM
connectors per
channel
DIMMs
installed in each
channel
DIMM type
DIMM speed
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
Unbuffered
DDR3 ECC
Single-rank,
dual-rank
v The following table lists the maximum DIMM population using ranked
UDIMMs.
Table 32. Maximum memory population using ranked UDIMMs (depending on your model)
Number of
UDIMMs
DIMM type
Single-rank UDIMMs 1 GB
4 GB
Dual-rank UDIMMs
2 GB
8 GB
Dual-rank UDIMMs
4 GB
16 GB
Dual-rank UDIMMs
8 GB
32 GB
Size
Total memory
v The following table shows the UDIMM memory population rule to optimize the
system performance.
Table 33. UDIMM population rule
DIMM connector 1
DIMM connector 2
DIMM connector 3
DIMM connector 4
Populated
Empty
Empty
Empty
Populated
Empty
Populated
Empty
Populated
Populated
Populated
Populated
177
Installing a DIMM
Use this information to install a DIMM.
DIMM 4
DIMM 3
DIMM 2
DIMM 1
Microprocessor
DIMM 4
DIMM 3
The following illustration shows the location of the DIMM connectors on the
system board.
DIMM 2
DIMM 1
Figure 44. The location of the DIMM connectors on the system board
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. Locate the DIMM connectors on the system board. Determine the connectors
into which you will install the DIMMs. Install the DIMMs in the sequence
shown in the following table.
178
1, 3
2, 4
5. Touch the static-protective package that contains the DIMM to any unpainted
metal surface on the outside of the server. Then, remove the DIMM from the
package.
6. Turn the DIMM so that the alignment slot align correctly with the alignment
tab.
7. Insert the DIMM into the connector by aligning the edges of the DIMM with
the slots at the ends of the DIMM connector.
8. Firmly press the DIMM straight down into the connector by applying pressure
on both ends of the DIMM simultaneously. The retaining clips snap into the
locked position when the DIMM is firmly seated in the connector.
Note: If there is a gap between the DIMM and the retaining clips, the DIMM
has not been correctly inserted; open the retaining clips, remove the DIMM,
and then reinsert it.
9. Reconnect any cable that you removed.
10. Reinstall the air baffle if it was removed before (see Replacing the air baffle
on page 64).
11. Reinstall the cover (see Replacing the cover on page 65).
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
179
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. Reconnect the power cord; then, turn on the server.
Attention: Operating the server for extended periods of time (more than 30
minutes) with the top cover removed might damage server components.
4. Determine which fan to replace by checking the LEDs on the system board (see
System-board LEDs on page 28); a lit LED indicates the fan to replace.
5. Turn off the server; then, disconnect the power cord again.
6. Remove the failed fan from the server:
a. Disconnect the fan cable from the system board. You may need to disengage
the cables from cable retention clips or cable holder. Note the routing of the
fan cable to the connector; you will have to route the fan cable the same
way when you install the fan.
b. Grasp the top of the fan with your index finger and thumb and lift the fan
out of the server.
180
Fan 1
Fan 2
Fan 3
Fan 4
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Position the replacement fan so that the airflow arrow on the fan points toward
the rear of the server.
181
Note: The correct airflow is from the front to the rear of the server.
Fan bracket
cable channel
Fan
Fan bracket
Fan bracket
cable slot
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
182
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 100C (212F)
Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
183
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. If necessary, lift the air baffle out of the way (see Removing the air baffle on
page 42).
3. Remove the system battery: The following illustration shows the location of the
system battery.
System board
error LED
Standby power
LED
Microprocessor
DIMM 2
DIMM 1
RTMM
Hearbeat LED
DIMM 4
DIMM 3
Microprocessor
error LED
DIMM 1 - 4
error LEDs
IMM2 hearbeat
LED
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.
c. Use your thumb and index finger to lift the battery from the socket.
184
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 100C (212F)
Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
185
Procedure
1. Follow any special handling and installation instructions that come with the
replacement battery.
2. Remove the cover (see Removing the cover on page 41).
3. If necessary, lift the air baffle out of the way (see Removing the air baffle on
page 42).
4. Insert the new battery:
a. Position the battery so that the positive (+) symbol is facing towards the
power supply.
b. Tilt the battery so that you can insert it into the socket on the side opposite
the battery clip.
c. Press the battery down into the socket until it snaps into place.
5.
6.
7.
8.
9.
d. If you removed a rubber cover from the battery holder, use your fingers to
install the battery cover on top of the battery connector.
Reinstall the air baffle (see Replacing the air baffle on page 64).
Reinstall the cover (see Replacing the cover on page 65).
Slide the server into the rack.
Reconnect the external cables and power cords; then, turn on the attached
devices and turn on the server.
Start the Setup utility and reset the configuration:
a. Set the system date and time.
b. Set the power-on password.
c. Reconfigure the server.
See Starting the Setup utility on page 74 for details.
186
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
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.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
187
Attention: If only one hot-swap power supply is installed in the server, you must
turn off the server before removing the power supply.
Procedure
1. Disconnect the power cord from the connector on the back of the power supply.
2. Press the orange release latch and hold it in place.
Power
supply
filler
Power
supply
Power
supply
release tab
3. Grasp the handle and pull the power supply out of the bay.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
188
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
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.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
Procedure
1. Grasp the side clip and pull to remove the power-supply filler panel from the
empty power-supply bay. Save the power-supply filler panel in case you
remove the power supply at a later time.
Important: During normal operation, each power-supply bay must contain
either a power supply or power-supply filler panel for proper cooling.
189
Power
supply
filler
Power
supply
Power
supply
release tab
2. Slide the hot-swap power supply into the bay until the release latch clicks into
place.
3. Connect one end of the power cord for the new power supply into the ac
connector on the back of the power supply; then, connect the other end of the
power cord into a properly grounded electrical outlet.
4. If the server is turned off, turn on the server.
5. Make sure that the ac power LED on the power supply is lit, indicating that the
power supply is operating correctly. If the server is turned on, make sure that
the dc power LED on the power supply is lit also.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
190
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. Pull out the cable from the optical drive cage connector.
Cable
connector
latch
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
191
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. Align the cable connector with the connector on the rear of the optical drive
cage.
4. Pull the cable connector latch up and hold it there while you slide the cable
connector to the locked position to lock the cable in place.
5. Connect the DVD cable into the connector on the rear of the optical drive cage.
6. Route the DVD signal cable through the fan cage hole on the left of fan 1. The
following illustration shows the cable routing for the DVD signal cable.
192
DVD drive
power cable
7. Secure the cable in the server using the cable tie and cable clip.
8. Reinstall the air baffle if it was removed before (see Replacing the air baffle
on page 64).
9. Reinstall the cover (see Replacing the cover on page 65).
What to do next
1. Slide the server into the rack.
2. Reconnect the power cords and cables that you removed.
3. Turn on all attached devices and the server.
193
Procedure
1. Remove the server cover (see Removing the cover on page 41).
2. Disconnect the signal cable from the operator information panel board.
3. Remove the screws that secure the operator information panel assembly to the
DVD drive housing.
4. Lift the operator information panel assembly out of the server.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
194
Procedure
1. Guide the operator information panel assembly into position on top of the
DVD drive housing. Make sure that the LEDs and the USB connectors are
aligned with the openings in the bezel and that the screw holes in the operator
information panel align with the screw holes in the top of the DVD bay
housing.
2. Use the screws that you removed in Removing the operator information panel
assembly on page 193 to secure the operator information panel assembly on
the DVD bay housing.
3.
4.
5.
6.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
195
Guide channels
Procedure
1. Turn off the server and peripheral devices and disconnect all power cords.
2. Remove the cover (see Removing the cover on page 41).
3. Pull the hard disk drives or fillers out of the server slightly to disengage them
from the backplate assembly. See Removing a simple-swap hard disk drive
on page 164 for details.
4. To obtain more working room, remove the fans (see Removing a system fan
on page 180).
5. Pull the hard disk drives out of the server slightly to disengage them from the
backplate assembly.
6. Lift the backplate assembly out of the server.
7. Make note of where the cables are attached to the backplate assembly; then,
disconnect them.
8. If you are instructed to return the backplate assembly, follow all packaging
instructions, and use any packaging materials for shipping that are supplied to
you.
196
Guide channels
Procedure
1. Reconnect the cables to the replacement backplate assembly.
2. Slide the backplate assembly into the guide channels, making sure that any
nearby wires or cables are not trapped or pinched.
3. Press on the two blue touch points firmly until the backplate assembly is fully
seated. .
4.
5.
6.
7.
197
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the hard disk drives out of the server (see Removing a hot-swap hard
disk drive on page 167 or Removing a simple-swap hard disk drive on page
164)
3. Disconnect the cable connections between the backplate and both the system
board and power supply (fixed or redundant).
Signal cables
Power cable
Figure 51. Software RAID signal cable routing for fixed power supply. (jinhu091)
198
Figure 52. Software RAID signal cable routing for redundant power supply. (jinhu091)
199
Signal cable
Figure 53. Hardware RAID signal cable routing for fixed power supply (Hardware RAID card
inserted on right side)
Signal cable
Figure 54. Hardware RAID signal cable routing for fixed power supply (Hardware RAID card
inserted on left side)
200
Power cable
Signal cable
Figure 56. Hardware RAID signal cable routing for redundant power supply (Hardware RAID
card inserted on right side)
201
Signal cable
Figure 57. Hardware RAID signal cable routing for redundant power supply (Hardware RAID
card inserted on left side)
Power cable
202
9. Reinstall the hard disk drives and filler panels (see Replacing a hot-swap hard
disk drive on page 168 and Replacing a simple-swap hard disk drive on
page 165).
What to do next
1. Slide the server into the rack.
2. Reconnect the power cords and cables that you removed.
3. Turn on all attached devices and the server.
Connectors
Connectors
Alignment
slots
Procedure
1. Turn off the server and peripheral devices and disconnect all power cords.
2. Remove the server from the rack and place it on a flat, static-protective surface.
3. Pull the hard disk drives out of the server slightly to disengage them from the
backplane.
4. Remove the cover (see Removing the cover on page 41).
Chapter 6. Removing and replacing components
203
Connectors
Connectors
Alignment
slots
Procedure
1. Reconnect the cables to the replacement backplate.
a. Connect the SAS/SATA controller signal cable to the backplane.
b. Connect the power cable to the backplane.
c. Connect the configuration cable to the backplane.
2. Slide the backplate into the guide channels, making sure that any nearby wires
or cables are not trapped or pinched.
204
3. Press on the blue touch point firmly until the backplane is fully seated and
clicks into place. The following illustrations shows the respective cable
connections when the hot-swap drive backplane is connected to a redundant
power supply or a fixed power supply.
Note: Make sure the relevant cables pass through the cable clips.
v Hot-swap backplane connected to fixed power supply:
Power cable
205
4.
5.
6.
7.
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 with one of these parts, contact a service
technician.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
206
Power supply
Rear screw
Procedure
1. Disconnect the ac power cord from the connector on the power supply that you
are removing. Disconnect all external cables.
2. Remove the cover (see Removing the cover on page 41).
Attention: To ensure proper cooling and airflow, do not operate the server for
more than 30 minutes with the top cover removed.
3. Remove the hard disk drive backplane or backplate assembly (see Removing
the simple-swap hard disk drive backplate assembly on page 195 or
Removing the hot-swap hard disk drive backplane on page 203).
4. Disconnect the power-supply cables from the connectors on the system board
and internal devices; then, disengage the cables from any retention-clips.
Note: Note the routing of all power-supply cables; you will route the
power-supply cables the same way when you install the power supply.
5. Remove the screw that holds the power supply to the rear of the chassis.
6. Loosen the captive thumbscrew that secures the rear of the power supply to the
chassis bottom.
7. Lift the power supply out of the bay.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
207
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 with one of these parts, contact a service
technician.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
208
Procedure
1. Place the new power supply into the bay.
Captive screw
Power supply
Rear screw
2. Tighten the captive thumbscrew that secures the rear of the power supply to
the chassis bottom.
3. Replace the screw that holds the power supply to the rear of the chassis.
4. Connect the internal power-supply cable from the power supply to the power
connectors on the system board. See System-board internal connectors for
the locations of the power connectors on the system board.
5. Route the internal power-supply cables, securing them with the
retention-clips.
6. Test the power supply:
a. Connect one end of the ac power cord for the new power supply into the
connector on the back of the power supply, and connect the other end of
the power cord into a properly grounded electrical outlet.
b. Make sure that the standby power LED on the system board is lit (see
System-board LEDs); if the standby power LED is not lit, discontinue
this procedure and obtain a new power supply.
c. Press the power-control button. Make sure that the power-on LED on the
front of the server is lit.
If the server starts, proceed to the next step. If the server does not start,
disconnect the ac power cord and call for service.
7. Turn off the server and disconnect the ac power cord.
8. Connect the cables from the power supply to the internal devices.
9. Install the hard disk drive backplane or backplate assembly (see Replacing
the simple-swap hard disk drive backplate assembly on page 196 or
Replacing the hot-swap hard disk drive backplane on page 204).
10. Reinstall the cover (see Replacing the cover on page 65).
11. Reconnect the ac power cord into the connector on the back of the power
supply.
12. Connect all external cables that you disconnected in "Removing the fixed
power supply".
Chapter 6. Removing and replacing components
209
13. Connect the other end of the ac power cord into a properly grounded
electrical outlet.
14. Press the power-control button.
15. Make sure that the power-on LED on the front of the server is lit.
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove any connected SAS/SATA signal cable and all other cables from the
safety cover.
SAS/SATA
signal cable
210
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
211
Procedure
1. Align the safety cover with the standoffs on the power paddle card and lower
the safety cover onto the power paddle card until it is secure.
212
Screws
3. Reconnect the SAS/SATA signal cable and all other cables that you have
removed previously.
SAS/SATA
signal cable
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
213
Procedure
1. Pull the power supplies out of the rear of the server, just enough to disengage
them from the server.
2. Remove the cover (see Removing the cover on page 41).
3. Remove the air baffle if installed (see Removing the air baffle on page 42).
4. Remove the 240 VA safety cover (see Removing the 240 VA safety cover on
page 210).
5. Loosen the cables from the cable tie.
6. Disconnect the power cables from the power connectors on the system board.
Power connectors
7. Disconnect the cables from the hard disk drive backplane or the backplate
assembly.
8. Disconnect the power cable from the DVD power cable (if available).
9. Lift the power paddle card up to remove it from the server.
214
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Procedure
1. Align the power paddle card with the standoffs on the system board and lower
the power paddle card onto the system board until it is secure.
215
2. Reinstall the safety cover (see Replacing the 240 VA safety cover on page
212).
3. Reconnect the power cable to the DVD power cable (if available).
4. Reconnect the cables to the hard disk drive backplane or the backplate
assembly.
5. Reconnect the power cables to power connectors on the system board.
Power connectors
216
What to do next
If you have replaced a server component or installed an optional device in the
server, you need to reconnect the power cords and all external cables, and turn on
the server and peripheral devices.
217
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle if installed (see Removing the air baffle on page 42).
3. Remove the heat sink:
CAUTION:
The heat sink may become very hot during normal operation. Allow time for
the heat sink to cool down before you touch it.
a. Loosen the screws and alternate among the screws until they break the seal
with the microprocessor.
b. Press firmly on the captive screws and loosen them with a screwdriver.
c. Use your fingers to gently pull the heat sink from the microprocessor.
Heat sink
System board
4. Lift the heat sink out of the server. After removal, place the heat sink on its
side on a clean, flat surface.
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.
5. Release the microprocessor retention latch by pressing down on the end,
moving it to the side, and releasing it to the open (up) position.
6. Open the microprocessor bracket frame by lifting up the tab on the top edge.
Keep the bracket frame in the open position.
Attention: Handle the microprocessor carefully. Dropping the microprocessor
during removal can damage the contacts. Also, contaminants on the
microprocessor contacts, such as oil from your skin, can cause connection
failures between the contacts and the socket.
218
Microprocessor
Alignment
marks
Microprocessor
bracket frame
Microprocessor
release lever
System board
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
219
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 222.
Note: Removing the heat sink from the microprocessor destroys the even
distribution of the thermal grease and requires replacing the thermal grease.
Attention:
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 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.
v The pins on the sockets are fragile. Any damage to the pins might require
replacing the system board.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
Procedure
1. Carefully turn the server on its side so that it is lying flat, with the cover facing
up.
Attention:
v 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 40.
v The microprocessor contacts are fragile; handle the microprocessor very
carefully. Do not touch the microprocessor contacts with your skin.
v The microprocessor fits only one way on the socket.
2. Align the microprocessor with the socket (note the alignment mark and the
position of the notches); then, carefully place the microprocessor on the socket,
close the microprocessor bracket frame, and close the microprocessor release
latch.
220
Heat sink
System board
221
What to do next
1. Slide the server into the rack.
2. Reconnect the power cords and cables that you removed.
3. Turn on all attached devices and the server.
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.
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.
222
0.02 mL of thermal
grease
Microprocessor
Note: 0.01 mL is one tick mark on the syringe. If the grease is properly applied,
approximately half (0.22 mL) of the grease will remain in the syringe.
6. Install the heat sink onto the microprocessor as described in Replacing a
microprocessor and heat sink on page 219.
223
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
System board
(7 screws)
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
Procedure
1. Remove the cover (see Removing the cover on page 41).
2. Remove the air baffle (see Removing the air baffle on page 42).
3. Remove the PCI riser-card assembly (see Removing the PCI riser-card
assembly on page 43).
4. Note where the cables are connected to the system board; then, disconnect
them.
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.
224
5. Remove any of the following components that are installed on the system
board and put them in a safe, static-protective place:
v Adapters (see Removing an adapter on page 156)
v DIMMs (see Removing a DIMM on page 175
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.
v Microprocessors and heat sinks (see Removing a microprocessor and heat
sink on page 217)
Note:
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.
v Battery (see Removing the system battery on page 183)
6. Remove the screws that secure the system board to the chassis, and put the
screws in a safe place.
7. Lift up the system board and carefully remove it from the server, being careful
not to damage any surrounding components.
What to do next
If you are instructed to return the server component or optional device, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
Attention: Make sure to place the socket cover for the microprocessor socket on
the system board before returning the system board.
225
4. Reactivate any Features on Demand features after replacing the system board.
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.
5. 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.
Read the safety information in Safety on page vii and Installation guidelines
on page 38.
If you are replacing a server component in the server, you need to turn off the
server and peripheral devices, and disconnect the power cords and all external
cables.
Procedure
1. Touch the static-protective package that contains the system board to any
unpainted metal surface on the server; then, remove the system board from
the package.
2. Align the system board with the chassis and replace the nine screws that you
removed.
System board
(7 screws)
3. Install any of the following components that you removed from the system
board:
226
4.
5.
6.
7.
8.
9.
10.
11.
Note: Make sure that none of the server cables are caught under the system
board.
v Microprocessor and heat sink (see Replacing a microprocessor and heat
sink on page 219)
v DIMMs (see Installing a DIMM on page 178)
v Adapters (see Replacing an adapter on page 157)
v Battery (see Replacing the system battery on page 185)
Reconnect any cables to the system board that you disconnected during
removal (see System-board internal connectors on page 25).
Reinstall the PCI riser-card assembly (see Replacing the PCI riser-card
assembly on page 63).
Reinstall the air baffle (see Replacing the air baffle on page 64).
Reinstall the cover (see Replacing the cover on page 65).
Push the power supplies back into the server.
Slide the server into the rack.
Reconnect the external cables and power cords; then, turn on the attached
devices and turn on the server.
Start the Setup utility and reset the configuration.
a. Set the system date and time.
b. Set the power-on password.
c. Reconfigure the server.
227
228
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:
Alert Category
Similar events are grouped together in categories. The alert category is in
the following format:
severity - device
severity is one of the following severity levels:
v Critical: A key component in the server is no longer functioning.
v Warning: The event might progress to a critical level.
v System: The event is the result of a system error or a configuration
change.
device is the specific device in the server that caused the event to be
generated.
Serviceable
Specifies whether user action is required to correct the problem.
Copyright IBM Corp. 2014
229
CIM Information
Provides the prefix of the message ID and the sequence number that is
used by the CIM message registry.
SNMP Trap ID
The SNMP trap ID that is found in the SNMP alert management
information base (MIB).
Automatically contact Service
If this field is set to Yes, and you have enabled Electronic Service Agent
(ESA), IBM Support will be notified automatically if the event is generated.
While you wait for IBM Support to call, you can perform the
recommended actions for the event.
User response
Indicates what actions you should perform to solve the event.
Perform the steps listed in this section in the order shown until the
problem is solved. After you perform all of the actions that are described
in this field, if you cannot solve the problem, contact IBM Support.
Note: This list includes error codes and messages that might not apply to
this machine type and model.
The following is the list of 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.
230
Event ID
Message String
Automatically
Notify
Support
40000086-00000000
Yes
40000087-00000000
Yes
80010202-0701ffff
Numeric sensor
[NumericSensorElementName] going low
(lower critical) has asserted. (CMOS
Battery)
Yes
80010902-0701ffff
Numeric sensor
[NumericSensorElementName] going high
(upper critical) has asserted.
Yes
806f0021-2582ffff
Fault in slot
Yes
[PhysicalConnectorSystemElementName] on
system [ComputerSystemElementName].
(All PCI Error)
Event ID
Message String
806f0021-3001ffff
Fault in slot
Yes
[PhysicalConnectorSystemElementName] on
system [ComputerSystemElementName].
(PCI 1)
806f0108-0a01ffff
Yes
806f0108-0a02ffff
Yes
806f010c-2001ffff
Yes
Uncorrectable error detected for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
1)
806f010c-2002ffff
Yes
Uncorrectable error detected for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
2)
806f010c-2003ffff
Yes
Uncorrectable error detected for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
3)
806f010c-2004ffff
Yes
Uncorrectable error detected for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
4)
806f010c-2581ffff
Yes
806f010d-0400ffff
Yes
806f010d-0401ffff
Yes
806f010d-0402ffff
Yes
806f010d-0403ffff
Yes
806f0207-0301ffff
Yes
806f020d-0400ffff
Yes
806f020d-0401ffff
Yes
231
232
Automatically
Notify
Support
Event ID
Message String
806f020d-0402ffff
Yes
806f020d-0403ffff
Yes
806f050c-2001ffff
806f050c-2002ffff
Yes
Memory Logging Limit Reached for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
2)
806f050c-2003ffff
Yes
Memory Logging Limit Reached for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
3)
806f050c-2004ffff
Yes
Memory Logging Limit Reached for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM
4)
806f050c-2581ffff
Yes
806f060d-0400ffff
Yes
806f060d-0401ffff
Yes
806f060d-0402ffff
Yes
806f060d-0403ffff
Yes
806f0813-0301ffff
Yes
806f0813-2581ffff
Yes
806f0813-2582ffff
Yes
40000001-00000000 40000003-00000000
40000001-00000000
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
Explanation: This message is for the use case when there is an error with an SSL Server, SSL Client, or SSL Trusted
CA Certificate.
May also be shown as 4000000200000000 or 0x4000000200000000
Severity: Error
Alert Category: System - SSL certification
Serviceable: No
CIM Information: Prefix: IMM and ID: 0002
SNMP Trap ID: 22
Automatically notify Support: No
User response: Make sure that the certificate that you are importing is correct and properly generated.
40000003-00000000
Explanation: This message is for the use case where a user modifies the Ethernet Port data rate.
May also be shown as 4000000300000000 or 0x4000000300000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0003
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
233
40000004-00000000 40000006-00000000
40000004-00000000
Explanation: This message is for the use case where A user modifies the Ethernet Port duplex setting.
May also be shown as 4000000400000000 or 0x4000000400000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0004
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000005-00000000
Explanation: This message is for the use case where a user modifies the Ethernet Port MTU setting.
May also be shown as 4000000500000000 or 0x4000000500000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0005
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
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.
May also be shown as 4000000600000000 or 0x4000000600000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0006
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
234
40000007-00000000 40000009-00000000
40000007-00000000
Explanation: This message is for the use case where a user enables or disabled the ethernet interface.
May also be shown as 4000000700000000 or 0x4000000700000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0007
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000008-00000000
Explanation: This message is for the use case where user modifies the Hostname of a Management Controller.
May also be shown as 4000000800000000 or 0x4000000800000000
Severity: Info
Alert Category: System - IMM Network event
Serviceable: No
CIM Information: Prefix: IMM and ID: 0008
SNMP Trap ID: 37
Automatically notify Support: No
User response: Information only; no action is required.
40000009-00000000
Explanation: This message is for the use case where user modifies the IP address of a Management Controller.
May also be shown as 4000000900000000 or 0x4000000900000000
Severity: Info
Alert Category: System - IMM Network event
Serviceable: No
CIM Information: Prefix: IMM and ID: 0009
SNMP Trap ID: 37
Automatically notify Support: No
User response: Information only; no action is required.
235
4000000a-00000000 4000000c-00000000
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
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0010
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000000b-00000000
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
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0011
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000000c-00000000
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
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0012
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
236
4000000d-00000000 4000000f-00000000
4000000d-00000000
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
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0013
SNMP Trap ID:
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
2.
Make sure that there is a DHCP server on the network that can assign an IP address to the IMM.
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
CIM Information: Prefix: IMM and ID: 0014
SNMP Trap ID: 30
Automatically notify Support: No
User response: Information only; no action is required.
4000000f-00000000
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
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0015
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
237
40000010-00000000 40000012-00000000
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.
May also be shown as 4000001000000000 or 0x4000001000000000
Severity: Warning
Alert Category: System - Remote Login
Serviceable: No
CIM Information: Prefix: IMM and ID: 0016
SNMP Trap ID: 30
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
Make sure that the correct login ID and password are being used.
2.
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.
May also be shown as 4000001100000000 or 0x4000001100000000
Severity: Warning
Alert Category: System - Remote Login
Serviceable: No
CIM Information: Prefix: IMM and ID: 0017
SNMP Trap ID: 30
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
Make sure that the correct login ID and password are being used.
2.
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.
May also be shown as 4000001200000000 or 0x4000001200000000
Severity: Info
Alert Category: System - Remote Login
Serviceable: No
CIM Information: Prefix: IMM and ID: 0018
SNMP Trap ID: 30
Automatically notify Support: No
User response: Make sure that the correct login ID and password are being used.
238
40000013-00000000 40000015-00000000
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.
May also be shown as 4000001300000000 or 0x4000001300000000
Severity: Info
Alert Category: System - Remote Login
Serviceable: No
CIM Information: Prefix: IMM and ID: 0019
SNMP Trap ID: 30
Automatically notify Support: No
User response: Make sure that the correct login ID and password are being used.
40000014-00000000
Explanation: This message is for the use case where a Management Controller Event Log on a system is cleared by
a user.
May also be shown as 4000001400000000 or 0x4000001400000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0020
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000015-00000000
Explanation: This message is for the use case where a Management Controller reset is initiated by a user.
May also be shown as 4000001500000000 or 0x4000001500000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0021
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
239
40000016-00000000 40000018-00000000
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.
May also be shown as 4000001600000000 or 0x4000001600000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0022
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000017-00000000
Explanation: This message is for the use case where a Management Controller IP address and configuration has
been assigned statically using user data.
May also be shown as 4000001700000000 or 0x4000001700000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0023
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000018-00000000
Explanation: This message is for the use case where a Management Controller ethernet interface is no longer active.
May also be shown as 4000001800000000 or 0x4000001800000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0024
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
240
40000019-00000000 4000001b-00000000
40000019-00000000
Explanation: This message is for the use case where a Management Controller ethernet interface is now active.
May also be shown as 4000001900000000 or 0x4000001900000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0025
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000001a-00000000
Explanation: This message is for the use case where a user changes the DHCP setting.
May also be shown as 4000001a00000000 or 0x4000001a00000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0026
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000001b-00000000
Explanation: This message is for the use case where a user restores a Management Controller configuration from a
file.
May also be shown as 4000001b00000000 or 0x4000001b00000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0027
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
241
4000001c-00000000 4000001d-00000000
4000001c-00000000
Explanation: This message is for the use case where an operating system error has occurred and the screen was
captured.
May also be shown as 4000001c00000000 or 0x4000001c00000000
Severity: Info
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0028
SNMP Trap ID: 22
Automatically notify Support: No
User response: If there was no operating-system error, complete the following steps until the problem is solved:
1.
2.
3.
Reinstall the RNDIS or cdc_ether device driver for the operating system.
4.
If there was an operating-system error, check the integrity of the installed operating system.
4000001d-00000000
Explanation: This message is for the use case where an operating system error has occurred and the screen capture
failed.
May also be shown as 4000001d00000000 or 0x4000001d00000000
Severity: Error
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0029
SNMP Trap ID: 22
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
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. 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.
242
4000001e-00000000 40000020-00000000
4000001e-00000000
Explanation: This message is for the use case where a Management Controller has resorted to running the backup
main application.
May also be shown as 4000001e00000000 or 0x4000001e00000000
Severity: Warning
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0030
SNMP Trap ID: 22
Automatically notify Support: No
User response: Update the IMM firmware. Important: Some cluster solutions require specific code levels or
coordinated code updates. If the device is part of a cluster solution, verify that the latest level of code is supported
for the cluster solution before you update the code.
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.
May also be shown as 4000001f00000000 or 0x4000001f00000000
Severity: Error
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0031
SNMP Trap ID: 22
Automatically notify Support: No
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
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.
May also be shown as 4000002000000000 or 0x4000002000000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0032
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
243
40000021-00000000 40000023-00000000
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.
May also be shown as 4000002100000000 or 0x4000002100000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0033
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
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.
May also be shown as 4000002200000000 or 0x4000002200000000
Severity: Error
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0034
SNMP Trap ID: 22
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
Make sure that the certificate that you are importing is correct.
2.
40000023-00000000
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.
May also be shown as 4000002300000000 or 0x4000002300000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0035
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
244
40000024-00000000 40000026-00000000
40000024-00000000
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.
May also be shown as 4000002400000000 or 0x4000002400000000
Severity: Info
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0036
SNMP Trap ID: 22
Automatically notify Support: No
User response: Information only; no action is required.
40000025-00000000
Explanation: This message is for the use case where a Management Controller Event Log on a system is 75% full.
May also be shown as 4000002500000000 or 0x4000002500000000
Severity: Info
Alert Category: System - Event Log 75% full
Serviceable: No
CIM Information: Prefix: IMM and ID: 0037
SNMP Trap ID: 35
Automatically notify Support: No
User response: Information only; no action is required.
40000026-00000000
Explanation: This message is for the use case where a Management Controller Event Log on a system is 100% full.
May also be shown as 4000002600000000 or 0x4000002600000000
Severity: Info
Alert Category: System - Event Log 75% full
Serviceable: No
CIM Information: Prefix: IMM and ID: 0038
SNMP Trap ID: 35
Automatically notify Support: No
User response: To avoid losing older log entries, save the log as a text file and clear the log.
245
40000027-00000000 40000029-00000000
40000027-00000000
Explanation: This message is for the use case when an implementation has detected a Platform Watchdog Timer
Expired
May also be shown as 4000002700000000 or 0x4000002700000000
Severity: Error
Alert Category: System - OS Timeout
Serviceable: No
CIM Information: Prefix: IMM and ID: 0039
SNMP Trap ID: 21
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
2.
3.
Reinstall the RNDIS or cdc_ether device driver for the operating system.
4.
5.
40000028-00000000
Explanation: This message is for the use case where a user has generated a Test Alert.
May also be shown as 4000002800000000 or 0x4000002800000000
Severity: Info
Alert Category: System - other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0040
SNMP Trap ID: 22
Automatically notify Support: No
User response: Information only; no action is required.
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.
May also be shown as 4000002900000000 or 0x4000002900000000
Severity: Info
Alert Category: System - Remote Login
Serviceable: No
CIM Information: Prefix: IMM and ID: 0041
SNMP Trap ID: 30
Automatically notify Support: No
User response: Complete the following steps until the problem is solved:
1.
Make sure that the correct login ID and password are being used.
2.
246
4000002a-00000000 4000002c-00000000
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.
May also be shown as 4000002a00000000 or 0x4000002a00000000
Severity: Error
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0042
SNMP Trap ID: 22
Automatically notify Support: No
User response: Reflash the IMM firmware to the latest version.
4000002b-00000000
247
4000002d-00000000 4000002f-00000000
4000002d-00000000
248
40000030-00000000 40000032-00000000
40000030-00000000
249
40000033-00000000 40000035-00000000
40000033-00000000
250
40000036-00000000 40000038-00000000
40000036-00000000
251
40000039-00000000 4000003b-00000000
40000039-00000000
IPv6 static address of network interface modified from [arg1] to [arg2] by user [arg3].
2.
Make sure that there is a DHCPv6 server on the network that can assign an IP address to the IMM.
252
4000003c-00000000 4000003e-00000000
4000003c-00000000
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.
5.
4000003d-00000000
253
4000003f-00000000 40000041-00000000
4000003f-00000000
CIM/XML HTTP port number changed from [arg1] to [arg2] by user [arg3].
254
40000042-00000000 40000044-00000000
40000042-00000000
CIM/XML HTTPS port number changed from [arg1] to [arg2] by user [arg3].
SNMP Agent port number changed from [arg1] to [arg2] by user [arg3].
SNMP Traps port number changed from [arg1] to [arg2] by user [arg3].
255
40000045-00000000 40000047-00000000
40000045-00000000
Remote Presence port number changed from [arg1] to [arg2] by user [arg3].
256
40000048-00000000 4000004a-00000000
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
May also be shown as 4000004800000000 or 0x4000004800000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0072
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000049-00000000
257
4000004b-00000000 4000004d-00000000
4000004b-00000000
258
4000004e-00000000 40000050-00000000
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
May also be shown as 4000004e00000000 or 0x4000004e00000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0078
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000004f-00000000 Date and Time set by user [arg1]: Date=[arg2], Time-[arg3], DST Auto-adjust=[arg4],
Timezone=[arg5].
Explanation: A user configured the Date and Time settings
May also be shown as 4000004f00000000 or 0x4000004f00000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0079
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
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
May also be shown as 4000005000000000 or 0x4000005000000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0080
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
259
40000051-00000000 40000053-00000000
40000051-00000000
260
40000054-00000000 40000056-00000000
40000054-00000000
261
40000057-00000000 40000059-00000000
40000057-00000000
262
4000005a-00000000 4000005c-00000000
4000005a-00000000
LAN over USB Port Forwarding set by user [arg1]: ExternalPort=[arg2], USB-LAN port=[arg3].
263
4000005d-00000000 4000005f-00000000
4000005d-00000000
264
40000060-00000000 40000062-00000000
40000060-00000000
265
40000063-00000000 40000065-00000000
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
May also be shown as 4000006300000000 or 0x4000006300000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0099
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000064-00000000
266
40000066-00000000 40000068-00000000
40000066-00000000
267
40000069-00000000 4000006b-00000000
40000069-00000000 User [arg1] for SNMPv3 set: AuthenticationProtocol=[arg2], PrivacyProtocol=[arg3],
AccessType=[arg4], HostforTraps=[arg5].
Explanation: User account SNMPv3 settings changed
May also be shown as 4000006900000000 or 0x4000006900000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0105
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
4000006a-00000000
268
4000006c-00000000 4000006e-00000000
4000006c-00000000
269
4000006f-00000000 40000071-00000000
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
May also be shown as 4000006f00000000 or 0x4000006f00000000
Severity: Info
Alert Category: none
Serviceable: No
CIM Information: Prefix: IMM and ID: 0111
SNMP Trap ID:
Automatically notify Support: No
User response: Information only; no action is required.
40000070-00000000
The power cap value changed from [arg1] watts to [arg2] watts by user [arg3].
270
40000072-00000000 40000074-00000000
40000072-00000000
The minimum power cap value changed from [arg1] watts to [arg2] watts.
The maximum power cap value changed from [arg1] watts to [arg2] watts.
The soft minimum power cap value changed from [arg1] watts to [arg2] watts.
271
40000075-00000000 40000077-00000000
40000075-00000000
The new minimum power cap value exceeded the power cap value.
272
40000078-00000000 4000007a-00000000
40000078-00000000
Static Power Savings mode has been turned off by user [arg1].
273
4000007b-00000000 4000007d-00000000
4000007b-00000000
Dynamic Power Savings mode has been turned off by user [arg1].
274
4000007e-00000000 40000080-00000000
4000007e-00000000
275
40000081-00000000 40000083-00000000
40000081-00000000
The measured power value has returned below the power cap value.
The new minimum power cap value has returned below the power cap value.
276
40000084-00000000 40000086-00000000
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
May also be shown as 4000008400000000 or 0x4000008400000000
Severity: Error
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0132
SNMP Trap ID: 22
Automatically notify Support: No
User response: Attempt to flash the IMM firmware to the same level on all nodes.
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
May also be shown as 4000008500000000 or 0x4000008500000000
Severity: Error
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0133
SNMP Trap ID: 22
Automatically notify Support: No
User response: Attempt to flash the FPGA firmware to the same level on all nodes.
40000086-00000000
277
40000087-00000000 40000089-00000000
40000087-00000000
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.
278
4000008a-00000000 80010002-0701ffff
4000008a-00000000 Management Controller [arg1]: Configuration restoration from a file by user [arg2] failed to
start..
Explanation: This message is for the use case where a user restores a Management Controller configuration from a
file and the restoration fails to start.
May also be shown as 4000008a00000000 or 0x4000008a00000000
Severity: Error
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: IMM and ID: 0138
SNMP Trap ID: 22
Automatically notify Support: No
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.
4000008b-00000000
Explanation: This message is for the use case where an IP address for the Storage Management has changed
May also be shown as 4000008b00000000 or 0x4000008b00000000
Severity: Info
Alert Category: System - IMM Network event
Serviceable: No
CIM Information: Prefix: IMM and ID: 0139
SNMP Trap ID: 37
Automatically notify Support: No
User response: Information only; no action is required.
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
Automatically notify Support: No
User response: Replace the system battery.
279
80010202-0701ffff 80010204-1d01ffff
80010202-0701ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (CMOS
Battery)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
May also be shown as 800102020701ffff or 0x800102020701ffff
Severity: Error
Alert Category: Critical - Voltage
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0480
SNMP Trap ID: 1
Automatically notify Support: Yes
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.
2.
3.
4.
(Trained technician only) Replace the system board. (n = power supply number)
80010204-1d01ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 1
Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
May also be shown as 800102041d01ffff or 0x800102041d01ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0480
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Reseat the failing fan n, which is indicated by a lit LED near the fan connector on the system board.
2.
280
80010204-1d02ffff 80010204-1d04ffff
80010204-1d02ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 2
Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
May also be shown as 800102041d02ffff or 0x800102041d02ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0480
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Reseat the failing fan n, which is indicated by a lit LED near the fan connector on the system board.
2.
80010204-1d03ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 3
Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
May also be shown as 800102041d03ffff or 0x800102041d03ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0480
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Reseat the failing fan n, which is indicated by a lit LED near the fan connector on the system board.
2.
80010204-1d04ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan 4
Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
May also be shown as 800102041d04ffff or 0x800102041d04ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0480
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Reseat the failing fan n, which is indicated by a lit LED near the fan connector on the system board.
Appendix A. Integrated Management Module II (IMM2) error messages
281
80010701-0701ffff 80010901-0701ffff
Replace the failing fan. (n = fan number)
2.
80010701-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted.
(Ambient Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Non-critical sensor
going high has asserted.
May also be shown as 800107010701ffff or 0x800107010701ffff
Severity: Warning
Alert Category: Warning - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0490
SNMP Trap ID: 12
Automatically notify Support: No
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 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.
4.
80010901-0701ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted.
(Ambient Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Critical sensor going
high has asserted.
May also be shown as 800109010701ffff or 0x800109010701ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0494
SNMP Trap ID: 0
Automatically notify Support: No
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 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.
4.
282
80010902-0701ffff 80010b01-0701ffff
80010902-0701ffff
Explanation: This message is for the use case when an implementation has detected an Upper Critical sensor going
high has asserted.
May also be shown as 800109020701ffff or 0x800109020701ffff
Severity: Error
Alert Category: Critical - Voltage
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0494
SNMP Trap ID: 1
Automatically notify Support: Yes
User response: If the specified sensor is Planar 3.3V or Planar 5V, (Trained technician only) replace the system
board. If the specified sensor is Planar 12V, complete the following steps until the problem is solved:
1.
2.
3.
(Trained technician only) Replace the system board. (n = power supply number)
Make sure that the fans are operating, that there are no obstructions to the airflow (front and rear of the server),
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.
4.
283
80030006-2101ffff 8007010f-2201ffff
80030006-2101ffff
Explanation: This message is for the use case when an implementation has detected a Sensor has deasserted.
May also be shown as 800300062101ffff or 0x800300062101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0509
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
80030012-2301ffff
Explanation: This message is for the use case when an implementation has detected a Sensor has deasserted.
May also be shown as 800300122301ffff or 0x800300122301ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0509
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
8007010f-2201ffff
Sensor [SensorElementName] has transitioned from normal to non-critical state. (GPT Status)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to
non-critical from normal.
May also be shown as 8007010f2201ffff or 0x8007010f2201ffff
Severity: Warning
Alert Category: Warning - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0520
SNMP Trap ID: 60
Automatically notify Support: No
User response:
1.
Check the IBM support site for service bulletins or firmware updates that apply to this GPT error.
2.
3.
284
80070201-0301ffff 80070201-2001ffff
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.
May also be shown as 800702010301ffff or 0x800702010301ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 0
Automatically notify Support: No
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.
80070201-2001ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (DIMM 1
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702012001ffff or 0x800702012001ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 0
Automatically notify Support: No
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.
285
80070201-2002ffff 80070201-2003ffff
80070201-2002ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (DIMM 2
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702012002ffff or 0x800702012002ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 0
Automatically notify Support: No
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.
80070201-2003ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (DIMM 3
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702012003ffff or 0x800702012003ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 0
Automatically notify Support: No
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.
286
80070201-2004ffff 80070202-0701ffff
80070201-2004ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (DIMM 4
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702012004ffff or 0x800702012004ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 0
Automatically notify Support: No
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.
80070202-0701ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd Vol
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702020701ffff or 0x800702020701ffff
Severity: Error
Alert Category: Critical - Voltage
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 1
Automatically notify Support: No
User response:
1.
2.
3.
4.
5.
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.
(Trained technician only) Replace the system board.
287
80070204-0a01ffff 80070208-0a01ffff
80070204-0a01ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 1 Fan
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702040a01ffff or 0x800702040a01ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-supply fan.
2.
80070204-0a02ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 2 Fan
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702040a02ffff or 0x800702040a02ffff
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 11
Automatically notify Support: No
User response:
1.
Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-supply fan.
2.
80070208-0a01ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 1 Therm
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702080a01ffff or 0x800702080a01ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 4
Automatically notify Support: No
User response:
1.
288
Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-supply fan.
System x3250 M4 Type 2583: Installation and Service Guide
80070208-0a02ffff 80070219-0701ffff
2.
3.
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.
Replace power supply n. (n = power supply number)
80070208-0a02ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 2 Therm
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702080a02ffff or 0x800702080a02ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 4
Automatically notify Support: No
User response:
1.
2.
3.
Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-supply fan.
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.
Replace power supply n. (n = power supply number)
80070219-0701ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
May also be shown as 800702190701ffff or 0x800702190701ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0522
SNMP Trap ID: 50
Automatically notify Support: No
User response:
1.
2.
3.
Check for the system firmware version and update 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.
4.
Unplug and restore AC power cord, then, perform step 1 and 2 again.
5.
If problems still occurred, (trained technician only) replace the system board.
289
80070301-0301ffff 80070608-0a01ffff
80070301-0301ffff Sensor [SensorElementName] has transitioned to non-recoverable 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
non-recoverable from less severe.
May also be shown as 800703010301ffff or 0x800703010301ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0524
SNMP Trap ID: 0
Automatically notify Support: No
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 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.
4.
80070608-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to
non-recoverable.
May also be shown as 800706080a01ffff or 0x800706080a01ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0530
SNMP Trap ID: 4
Automatically notify Support: No
User response: If the specified sensor is PS n 12V OC Fault, complete the following steps until the problem is
solved:
1.
Use the IBM Power Configurator utility to determine current system power consumption. For more information
and to download the utility, go to http://www-03.ibm.com/systems/bladecenter/resources/powerconfig.html.
2.
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
1.
2.
3.
(Trained technician only) Replace the system board. (n = power supply number)
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
1.
2.
3.
4.
(Trained technician only) Replace the system board. (n = power supply number)
290
80070608-0a02ffff
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
1.
2.
80070608-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to
non-recoverable.
May also be shown as 800706080a02ffff or 0x800706080a02ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0530
SNMP Trap ID: 4
Automatically notify Support: No
User response: If the specified sensor is PS n 12V OC Fault, complete the following steps until the problem is
solved:
1.
2.
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.
Follow actions in "Power Problems and Solving Power Problems".
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
1.
2.
3.
(Trained technician only) Replace the system board. (n = power supply number)
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
1.
2.
3.
4.
(Trained technician only) Replace the system board. (n = power supply number)
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
1.
2.
291
80080128-2101ffff 806f0007-0301ffff
80080128-2101ffff
Explanation: This message is for the use case when an implementation has detected a Device was inserted.
May also be shown as 800801282101ffff or 0x800801282101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0536
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
800b0108-1301ffff
Explanation: This message is for the use case when Redundancy Lost has asserted.
May also be shown as 800b01081301ffff or 0x800b01081301ffff
Severity: Error
Alert Category: Critical - Redundant Power Supply
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0802
SNMP Trap ID: 9
Automatically notify Support: No
User response:
1.
2.
806f0007-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor Failed - IERR
Condition.
May also be shown as 806f00070301ffff or 0x806f00070301ffff
Severity: Error
Alert Category: Critical - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0042
SNMP Trap ID: 40
Automatically notify Support: No
User response:
1.
Update the latest level of system firmware and device drivers are installed for all adapters and standard devices,
such as UEFI, IMM Ethernet,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
supported for the cluster solution before you update the code.
2.
3.
4.
5.
292
806f0008-0a01ffff 806f0009-1301ffff
6.
Explanation: This message is for the use case when an implementation has detected a Power Unit that has been
Disabled.
May also be shown as 806f00091301ffff or 0x806f00091301ffff
Severity: Info
Alert Category: System - Power Off
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0106
SNMP Trap ID: 23
Automatically notify Support: No
User response: No action; information only.
293
806f000d-0400ffff 806f000d-0402ffff
806f000d-0400ffff
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
CIM Information: Prefix: PLAT and ID: 0162
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
806f000d-0401ffff
Explanation: This message is for the use case when an implementation has detected a Drive has been Added.
May also be shown as 806f000d0401ffff or 0x806f000d0401ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0162
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
806f000d-0402ffff
Explanation: This message is for the use case when an implementation has detected a Drive has been Added.
May also be shown as 806f000d0402ffff or 0x806f000d0402ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0162
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
294
806f000d-0403ffff 806f000f-220102ff
806f000d-0403ffff
Explanation: This message is for the use case when an implementation has detected a Drive has been Added.
May also be shown as 806f000d0403ffff or 0x806f000d0403ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0162
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
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
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0794
SNMP Trap ID: 41
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
806f000f-220102ff
Explanation: This message is for the use case when an implementation has detected that the usable Memory is
insufficient for operation.
May also be shown as 806f000f220102ff or 0x806f000f220102ff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0132
SNMP Trap ID: 41
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
295
806f000f-220103ff 806f000f-220107ff
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.
May also be shown as 806f000f220103ff or 0x806f000f220103ff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0770
SNMP Trap ID: 5
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
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.
May also be shown as 806f000f220104ff or 0x806f000f220104ff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0795
SNMP Trap ID: 50
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
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.
May also be shown as 806f000f220107ff or 0x806f000f220107ff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0764
SNMP Trap ID: 50
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
296
806f000f-22010aff 806f000f-22010bff
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
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0766
SNMP Trap ID: 50
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
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
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0850
SNMP Trap ID: 40
Automatically notify Support: No
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 to the latest level (see Updating the firmware). Important: Some cluster solutions
require specific code levels or coordinated code updates. If the device is part of a cluster solution, verify that the
latest level of code is supported for the cluster solution before you update the code.
4.
Remove components one at a time, restarting the server each time, to see if the problem goes away.
5.
If the problem remains, (trained service technician) replace the system board.
Firmware Error :
297
806f000f-22010cff 806f0013-1701ffff
806f000f-22010cff
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
Alert Category: Critical - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0050
SNMP Trap ID: 40
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
806f000f-2201ffff
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
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0184
SNMP Trap ID: 50
Automatically notify Support: No
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 diagnostic code in the "UEFI diagnostic code" section of the Info Center
for the appropriate user response. Firmware Error :
806f0013-1701ffff
Explanation: This message is for the use case when an implementation has detected a Front Panel NMI / Diagnostic
Interrupt.
May also be shown as 806f00131701ffff or 0x806f00131701ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0222
SNMP Trap ID: 50
Automatically notify Support: No
User response: If the NMI button has not been pressed, complete the following steps:
1.
2.
3.
298
806f0021-2582ffff 806f0021-3001ffff
806f0021-2582ffff Fault in slot [PhysicalConnectorSystemElementName] on system
[ComputerSystemElementName]. (All PCI Error)
Explanation: This message is for the use case when an implementation has detected a Fault in a slot.
May also be shown as 806f00212582ffff or 0x806f00212582ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0330
SNMP Trap ID: 50
Automatically notify Support: Yes
User response:
1.
2.
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
level of code is supported for the cluster solution before you update the code.
4.
5.
6.
2.
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
level of code is supported for the cluster solution before you update the code.
4.
5.
6.
PCI 2 :
299
806f0023-2101ffff 806f0108-0a01ffff
806f0023-2101ffff
Explanation: This message is for the use case when an implementation has detected a Watchdog Timer Expired.
May also be shown as 806f00232101ffff or 0x806f00232101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0368
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0107-0301ffff
Explanation: This message is for the use case when an implementation has detected an Over-Temperature Condition
Detected for Processor.
May also be shown as 806f01070301ffff or 0x806f01070301ffff
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0036
SNMP Trap ID: 0
Automatically notify Support: No
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.
2.
Make sure that the heat sink for microprocessor n is installed correctly.
3.
806f0108-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply has failed.
May also be shown as 806f01080a01ffff or 0x806f01080a01ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0086
SNMP Trap ID: 4
Automatically notify Support: Yes
User response:
1.
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)
300
806f0108-0a02ffff 806f010c-2001ffff
806f0108-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply has failed.
May also be shown as 806f01080a02ffff or 0x806f01080a02ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0086
SNMP Trap ID: 4
Automatically notify Support: Yes
User response:
1.
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
Explanation: This message is for the use case when an implementation has detected a Power Unit that has been
power cycled.
May also be shown as 806f01091301ffff or 0x806f01091301ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0108
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 806f010c2001ffff or 0x806f010c2001ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0138
SNMP Trap ID: 41
Automatically notify Support: Yes
User response:
1.
2.
3.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
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.
If the problem follows the DIMM, replace the failing DIMM.
301
806f010c-2002ffff
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
(Trained Service technician only) Replace the affected microprocessor.
8.
1.
2.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
8.
302
806f010c-2003ffff 806f010c-2004ffff
806f010c-2003ffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error.
May also be shown as 806f010c2003ffff or 0x806f010c2003ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0138
SNMP Trap ID: 41
Automatically notify Support: Yes
User response:
1.
2.
3.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
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.
If the problem follows the DIMM, replace the failing DIMM.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
6.
7.
8.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
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.
If the problem follows the DIMM, replace the failing DIMM.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
6.
303
806f010c-2581ffff 806f010d-0400ffff
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
(Trained Service technician only) Replace the affected microprocessor.
8.
1.
2.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
(Trained Service technician only) Replace the affected microprocessor.
8.
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.
May also be shown as 806f010d0400ffff or 0x806f010d0400ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0164
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
Run the hard disk drive diagnostic test on drive n.
1.
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
304
806f010d-0401ffff 806f010d-0402ffff
3.
Replace the following components one at a time, in the order shown, restarting the server each time: a. Hard
disk drive b. Cable from the system board to the backplane c. Hard disk drive backplane (n = hard disk drive
number)
806f010d-0401ffff
The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 1)
Explanation: This message is for the use case when an implementation has detected a Drive was Disabled due to
fault.
May also be shown as 806f010d0401ffff or 0x806f010d0401ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0164
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
2.
Reseat the following components: a. Hard disk drive (wait 1 minute or more before reinstalling the drive) b.
Cable from the system board to the backplane
3.
Replace the following components one at a time, in the order shown, restarting the server each time: a. Hard
disk drive b. Cable from the system board to the backplane c. Hard disk drive backplane (n = hard disk drive
number)
806f010d-0402ffff
The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 2)
Explanation: This message is for the use case when an implementation has detected a Drive was Disabled due to
fault.
May also be shown as 806f010d0402ffff or 0x806f010d0402ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0164
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
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)
305
806f010d-0403ffff 806f010f-2201ffff
806f010d-0403ffff
The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 3)
Explanation: This message is for the use case when an implementation has detected a Drive was Disabled due to
fault.
May also be shown as 806f010d0403ffff or 0x806f010d0403ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0164
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
Run the hard disk drive diagnostic test on drive n.
1.
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)
806f010f-2201ffff
Explanation: This message is for the use case when an implementation has detected a System Firmware Hang.
May also be shown as 806f010f2201ffff or 0x806f010f2201ffff
Severity: Error
Alert Category: System - Boot failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0186
SNMP Trap ID: 25
Automatically notify Support: No
User response:
Make sure the server meets the minimum configuration to start (see Power-supply LEDs).
1.
2.
Update the server firmware on the primary page. Important: Some cluster solutions require specific code levels
or coordinated code updates. If the device is part of a cluster solution, verify that the latest level of code is
supported for the cluster solution before you update the code.
3.
306
806f0123-2101ffff 806f0125-1d02ffff
806f0123-2101ffff Reboot of system [ComputerSystemElementName] initiated by [WatchdogElementName].
(Watchdog)
Explanation: This message is for the use case when an implementation has detected a Reboot by a Watchdog
occurred.
May also be shown as 806f01232101ffff or 0x806f01232101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0370
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0125-1d01ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is Absent.
May also be shown as 806f01251d01ffff or 0x806f01251d01ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0392
SNMP Trap ID:
Automatically notify Support: No
User response: Please ensure the PCI riser 1 has been installed correctly.
806f0125-1d02ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is Absent.
May also be shown as 806f01251d02ffff or 0x806f01251d02ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0392
SNMP Trap ID:
Automatically notify Support: No
User response: Please ensure the PCI riser 1 has been installed correctly.
307
806f0125-1d03ffff 806f0207-0301ffff
806f0125-1d03ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is Absent.
May also be shown as 806f01251d03ffff or 0x806f01251d03ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0392
SNMP Trap ID:
Automatically notify Support: No
User response: Please ensure the PCI riser 1 has been installed correctly.
806f0125-1d04ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is Absent.
May also be shown as 806f01251d04ffff or 0x806f01251d04ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0392
SNMP Trap ID:
Automatically notify Support: No
User response: Please ensure the PCI riser 1 has been installed correctly.
806f0207-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST
condition.
May also be shown as 806f02070301ffff or 0x806f02070301ffff
Severity: Error
Alert Category: Critical - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0044
SNMP Trap ID: 40
Automatically notify Support: Yes
User response:
1.
Update the latest level of system firmware and device drivers are installed for all adapters and standard devices,
such as UEFI, IMM Ethernet,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
supported for the cluster solution before you update the code.
2.
3.
4.
5.
6.
308
806f020d-0400ffff 806f020d-0401ffff
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.
May also be shown as 806f020d0400ffff or 0x806f020d0400ffff
Severity: Warning
Alert Category: System - Predicted Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0168
SNMP Trap ID: 27
Automatically notify Support: Yes
User response:
1.
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)
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)
309
806f020d-0402ffff 806f020d-0403ffff
806f020d-0402ffff Failure Predicted on drive [StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive 2)
Explanation: This message is for the use case when an implementation has detected an Array Failure is Predicted.
May also be shown as 806f020d0402ffff or 0x806f020d0402ffff
Severity: Warning
Alert Category: System - Predicted Failure
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0168
SNMP Trap ID: 27
Automatically notify Support: Yes
User response:
Run the hard disk drive diagnostic test on drive n.
1.
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)
1.
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)
310
806f0223-2101ffff 806f0308-0a02ffff
806f0223-2101ffff Powering off system [ComputerSystemElementName] initiated by [WatchdogElementName].
(Watchdog)
Explanation: This message is for the use case when an implementation has detected a Poweroff by Watchdog has
occurred.
May also be shown as 806f02232101ffff or 0x806f02232101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0372
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0308-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply that has input
that has been lost.
May also be shown as 806f03080a01ffff or 0x806f03080a01ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0100
SNMP Trap ID:
Automatically notify Support: No
User response:
1.
2.
3.
806f0308-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply that has input
that has been lost.
May also be shown as 806f03080a02ffff or 0x806f03080a02ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0100
SNMP Trap ID:
Automatically notify Support: No
User response:
1.
2.
3.
311
806f030c-2001ffff 806f030c-2002ffff
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.
May also be shown as 806f030c2001ffff or 0x806f030c2001ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0136
SNMP Trap ID: 41
Automatically notify Support: No
User response: Note: Each time you install or remove a DIMM, you must disconnect the server from the power
source; then, wait 10 seconds before restarting the server.
1.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
2.
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.
If the problem follows the DIMM, replace the failing DIMM.
4.
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.
(Trained technician only) Replace the affected microprocessor.
7.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
2.
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.
If the problem follows the DIMM, replace the failing DIMM.
4.
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.
312
806f030c-2003ffff 806f030c-2004ffff
806f030c-2003ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].
(DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory Scrub failure.
May also be shown as 806f030c2003ffff or 0x806f030c2003ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0136
SNMP Trap ID: 41
Automatically notify Support: No
User response: Note: Each time you install or remove a DIMM, you must disconnect the server from the power
source; then, wait 10 seconds before restarting the server.
1.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
2.
3.
4.
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.
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.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
2.
3.
4.
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.
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.
313
806f0313-1701ffff 806f040c-2001ffff
806f0313-1701ffff
Explanation: This message is for the use case when an implementation has detected a Software NMI.
May also be shown as 806f03131701ffff or 0x806f03131701ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0228
SNMP Trap ID: 50
Automatically notify Support: No
User response:
1.
2.
3.
4.
Explanation: This message is for the use case when an implementation has detected that Memory has been
Disabled.
May also be shown as 806f040c2001ffff or 0x806f040c2001ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0131
SNMP Trap ID:
Automatically notify Support: No
User response:
Make sure the DIMM is installed correctly.
1.
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.
314
806f040c-2002ffff 806f040c-2003ffff
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
Explanation: This message is for the use case when an implementation has detected that Memory has been
Disabled.
May also be shown as 806f040c2002ffff or 0x806f040c2002ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0131
SNMP Trap ID:
Automatically notify Support: No
User response:
1.
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-2003ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been
Disabled.
May also be shown as 806f040c2003ffff or 0x806f040c2003ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0131
SNMP Trap ID:
Automatically notify Support: No
User response:
1.
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).
315
806f040c-2004ffff 806f040c-2581ffff
806f040c-2004ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been
Disabled.
May also be shown as 806f040c2004ffff or 0x806f040c2004ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0131
SNMP Trap ID:
Automatically notify Support: No
User response:
Make sure the DIMM is installed correctly.
1.
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-2581ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been
Disabled.
May also be shown as 806f040c2581ffff or 0x806f040c2581ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0131
SNMP Trap ID:
Automatically notify Support: No
User response:
Make sure the DIMM is installed correctly.
1.
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).
316
806f0413-2582ffff 806f0507-0301ffff
806f0413-2582ffff
Explanation: This message is for the use case when an implementation has detected a PCI PERR.
May also be shown as 806f04132582ffff or 0x806f04132582ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0232
SNMP Trap ID: 50
Automatically notify Support: No
User response:
1.
2.
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
level of code is supported for the cluster solution before you update the code.
4.
5.
6.
806f0507-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor Configuration
Mismatch has occurred.
May also be shown as 806f05070301ffff or 0x806f05070301ffff
Severity: Error
Alert Category: Critical - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0062
SNMP Trap ID: 40
Automatically notify Support: No
User response:
1.
2.
Check the CPU LED. See more information about the CPU LED in Light path diagnostics.
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.
3.
Make sure that the installed microprocessors are compatible with each other.
4.
5.
317
806f050c-2001ffff 806f050c-2002ffff
806f050c-2001ffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Reached.
May also be shown as 806f050c2001ffff or 0x806f050c2001ffff
Severity: Warning
Alert Category: Warning - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0144
SNMP Trap ID: 43
Automatically notify Support: Yes
User response:
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
1.
2.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
(Trained Service technician only) Replace the affected microprocessor.
8.
1.
2.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
318
806f050c-2003ffff 806f050c-2004ffff
6.
7.
8.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
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.
If the problem follows the DIMM, replace the failing DIMM.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
6.
7.
8.
Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
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.
Appendix A. Integrated Management Module II (IMM2) error messages
319
806f050c-2581ffff
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
(Trained Service technician only) Replace the affected microprocessor.
8.
1.
2.
Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
If the problem follows the DIMM, replace the failing DIMM.
3.
4.
(Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM connector. If the
connector contains any foreign material or is damaged, replace the system board.
5.
(Trained technician only) Remove the affected microprocessor and check the microprocessor socket pins for any
damaged pins. If a damage is found, replace the system board.
(Trained technician only) Replace the affected microprocessor.
6.
7.
Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the power source and restart the
server.
8.
320
806f050d-0400ffff 806f050d-0401ffff
806f050d-0400ffff
Explanation: This message is for the use case when an implementation has detected that an Array is Critical.
May also be shown as 806f050d0400ffff or 0x806f050d0400ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0174
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
6.
Replace the hard disk drive that is indicated by a lit status LED.
806f050d-0401ffff
Explanation: This message is for the use case when an implementation has detected that an Array is Critical.
May also be shown as 806f050d0401ffff or 0x806f050d0401ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0174
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
6.
Replace the hard disk drive that is indicated by a lit status LED.
321
806f050d-0402ffff 806f050d-0403ffff
806f050d-0402ffff
Explanation: This message is for the use case when an implementation has detected that an Array is Critical.
May also be shown as 806f050d0402ffff or 0x806f050d0402ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0174
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
6.
Replace the hard disk drive that is indicated by a lit status LED.
806f050d-0403ffff
Explanation: This message is for the use case when an implementation has detected that an Array is Critical.
May also be shown as 806f050d0403ffff or 0x806f050d0403ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0174
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
6.
Replace the hard disk drive that is indicated by a lit status LED.
322
806f0513-2582ffff 806f052b-2101ffff
806f0513-2582ffff
Explanation: This message is for the use case when an implementation has detected a PCI SERR.
May also be shown as 806f05132582ffff or 0x806f05132582ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0234
SNMP Trap ID: 50
Automatically notify Support: No
User response:
1.
2.
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
level of code is supported for the cluster solution before you update the code.
4.
Make sure that the adapter is supported. For a list of supported optional devices, see http://www.ibm.com/
systems/info/x86servers/serverproven/compat/us/.
5.
6.
7.
Make sure the server meets the minimum configuration to start (see Power-supply LEDs).
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
require specific code levels or coordinated code updates. If the device is part of a cluster solution, verify that the
latest level of code is supported for the cluster solution before you update the code.
4.
Remove components one at a time, restarting the server each time, to see if the problem goes away.
5.
If the problem remains, (trained service technician) replace the system board.
323
806f0607-0301ffff 806f0608-0a01ffff
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.
May also be shown as 806f06070301ffff or 0x806f06070301ffff
Severity: Error
Alert Category: Critical - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0816
SNMP Trap ID: 40
Automatically notify Support: No
User response:
1.
Update the latest level of system firmware and device drivers are installed for all adapters and standard devices,
such as UEFI, IMM Ethernet,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
supported for the cluster solution before you update the code.
2.
3.
4.
5.
6.
806f0608-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply with a
Configuration Error.
May also be shown as 806f06080a01ffff or 0x806f06080a01ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0104
SNMP Trap ID: 4
Automatically notify Support: No
User response:
1.
Make sure that the power supplies installed are with the same rating or wattage.
2.
324
806f0608-0a02ffff 806f060d-0400ffff
806f0608-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply with a
Configuration Error.
May also be shown as 806f06080a02ffff or 0x806f06080a02ffff
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0104
SNMP Trap ID: 4
Automatically notify Support: No
User response:
1.
Make sure that the power supplies installed are with the same rating or wattage.
2.
806f060d-0400ffff
Explanation: This message is for the use case when an implementation has detected that an Array Failed.
May also be shown as 806f060d0400ffff or 0x806f060d0400ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0176
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
Replace the hard disk drive that is indicated by a lit status LED.
325
806f060d-0401ffff 806f060d-0402ffff
806f060d-0401ffff
Explanation: This message is for the use case when an implementation has detected that an Array Failed.
May also be shown as 806f060d0401ffff or 0x806f060d0401ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0176
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
Replace the hard disk drive that is indicated by a lit status LED.
806f060d-0402ffff
Explanation: This message is for the use case when an implementation has detected that an Array Failed.
May also be shown as 806f060d0402ffff or 0x806f060d0402ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0176
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
Replace the hard disk drive that is indicated by a lit status LED.
326
806f060d-0403ffff 806f070c-2002ffff
806f060d-0403ffff
Explanation: This message is for the use case when an implementation has detected that an Array Failed.
May also be shown as 806f060d0403ffff or 0x806f060d0403ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0176
SNMP Trap ID: 5
Automatically notify Support: Yes
User response:
1.
Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2.
3.
4.
5.
Replace the hard disk drive that is indicated by a lit status LED.
327
806f070c-2003ffff 806f070c-2581ffff
806f070c-2003ffff Configuration Error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has been corrected.
May also be shown as 806f070c2003ffff or 0x806f070c2003ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0126
SNMP Trap ID: 41
Automatically notify Support: No
User response: Make sure that DIMMs are installed and following the memory population chart in the system
publication.
806f070c-2004ffff Configuration Error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 4)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has been corrected.
May also be shown as 806f070c2004ffff or 0x806f070c2004ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0126
SNMP Trap ID: 41
Automatically notify Support: No
User response: Make sure that DIMMs are installed and following the memory population chart in the system
publication.
806f070c-2581ffff Configuration Error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (All DIMMS)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has been corrected.
May also be shown as 806f070c2581ffff or 0x806f070c2581ffff
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0126
SNMP Trap ID: 41
Automatically notify Support: No
User response: Make sure that DIMMs are installed and following the memory population chart in the system
publication. One of the DIMMs :
328
806f070d-0400ffff 806f070d-0402ffff
806f070d-0400ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
May also be shown as 806f070d0400ffff or 0x806f070d0400ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0178
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f070d-0401ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
May also be shown as 806f070d0401ffff or 0x806f070d0401ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0178
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f070d-0402ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
May also be shown as 806f070d0402ffff or 0x806f070d0402ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0178
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
329
806f070d-0403ffff 806f0813-0301ffff
806f070d-0403ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
May also be shown as 806f070d0403ffff or 0x806f070d0403ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0178
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0807-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor has been Disabled.
May also be shown as 806f08070301ffff or 0x806f08070301ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0061
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0813-0301ffff
Explanation: This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
May also be shown as 806f08130301ffff or 0x806f08130301ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0240
SNMP Trap ID: 50
Automatically notify Support: Yes
User response:
Check the system-event log.
1.
2.
(Trained technician only) Remove the failing microprocessor from the system board (see Removing a
microprocessor and heat sink).
3.
Check for a server firmware update. Important: Some cluster solutions require specific code levels or coordinated
code updates. If the device is part of a cluster solution, verify that the latest level of code is supported for the
cluster solution before you update the code.
4.
330
806f0813-2581ffff 806f0813-2582ffff
806f0813-2581ffff
Explanation: This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
May also be shown as 806f08132581ffff or 0x806f08132581ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0240
SNMP Trap ID: 50
Automatically notify Support: Yes
User response:
1.
2.
3.
4.
Check for a server firmware update. Important: Some cluster solutions require specific code levels or coordinated
code updates. If the device is part of a cluster solution, verify that the latest level of code is supported for the
cluster solution before you update the code.
5.
Make sure that the installed DIMMs are supported and configured correctly.
6.
806f0813-2582ffff
Explanation: This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
May also be shown as 806f08132582ffff or 0x806f08132582ffff
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0240
SNMP Trap ID: 50
Automatically notify Support: Yes
User response:
1.
2.
3.
4.
5.
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.
(Trained technician only) Replace the system board.
331
806f0823-2101ffff 81010002-0701ffff
806f0823-2101ffff
Explanation: This message is for the use case when an implementation has detected a Watchdog Timer interrupt
occurred.
May also be shown as 806f08232101ffff or 0x806f08232101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0376
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
806f0a07-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor is running in the
Degraded state.
May also be shown as 806f0a070301ffff or 0x806f0a070301ffff
Severity: Warning
Alert Category: Warning - CPU
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0038
SNMP Trap ID: 42
Automatically notify Support: No
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.
3.
Make sure that the heat sink for microprocessor n is installed correctly.
4.
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.
May also be shown as 810100020701ffff or 0x810100020701ffff
Severity: Info
Alert Category: Warning - Voltage
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0477
SNMP Trap ID: 13
Automatically notify Support: No
User response: No action; information only.
332
81010202-0701ffff 81010204-1d02ffff
81010202-0701ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted.
(CMOS Battery)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has deasserted.
May also be shown as 810102020701ffff or 0x810102020701ffff
Severity: Info
Alert Category: Critical - Voltage
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0481
SNMP Trap ID: 1
Automatically notify Support: No
User response: No action; information only. SysBrd 12V : SysBrd 3.3V : SysBrd 5V :
81010204-1d01ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted. (Fan
1 Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has deasserted.
May also be shown as 810102041d01ffff or 0x810102041d01ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0481
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
81010204-1d02ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted. (Fan
2 Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has deasserted.
May also be shown as 810102041d02ffff or 0x810102041d02ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0481
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
333
81010204-1d03ffff 81010701-0701ffff
81010204-1d03ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted. (Fan
3 Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has deasserted.
May also be shown as 810102041d03ffff or 0x810102041d03ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0481
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
81010204-1d04ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted. (Fan
4 Tach)
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has deasserted.
May also be shown as 810102041d04ffff or 0x810102041d04ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0481
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
81010701-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has deasserted.
(Ambient Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Non-critical sensor
going high has deasserted.
May also be shown as 810107010701ffff or 0x810107010701ffff
Severity: Info
Alert Category: Warning - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0491
SNMP Trap ID: 12
Automatically notify Support: No
User response: No action; information only.
334
81010901-0701ffff 81010b01-0701ffff
81010901-0701ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(Ambient Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Critical sensor going
high has deasserted.
May also be shown as 810109010701ffff or 0x810109010701ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0495
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
81010902-0701ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(SysBrd 12V)
Explanation: This message is for the use case when an implementation has detected an Upper Critical sensor going
high has deasserted.
May also be shown as 810109020701ffff or 0x810109020701ffff
Severity: Info
Alert Category: Critical - Voltage
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0495
SNMP Trap ID: 1
Automatically notify Support: No
User response: No action; information only. SysBrd 3.3V : SysBrd 5V :
81010b01-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has
deasserted. (Ambient Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Non-recoverable
sensor going high has deasserted.
May also be shown as 81010b010701ffff or 0x81010b010701ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0499
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
335
81030006-2101ffff 8107010f-2201ffff
81030006-2101ffff
Explanation: This message is for the use case when an implementation has detected a Sensor has asserted.
May also be shown as 810300062101ffff or 0x810300062101ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0508
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
81030012-2301ffff
Explanation: This message is for the use case when an implementation has detected a Sensor has asserted.
May also be shown as 810300122301ffff or 0x810300122301ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0508
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
8107010f-2201ffff Sensor [SensorElementName] has deasserted the transition from normal to non-critical state.
(GPT 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.
May also be shown as 8107010f2201ffff or 0x8107010f2201ffff
Severity: Info
Alert Category: Warning - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0521
SNMP Trap ID: 60
Automatically notify Support: No
User response: No action; information only.
336
81070201-0301ffff 81070201-2002ffff
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.
May also be shown as 810702010301ffff or 0x810702010301ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
81070201-2001ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (DIMM 1
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702012001ffff or 0x810702012001ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
81070201-2002ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (DIMM 2
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702012002ffff or 0x810702012002ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
337
81070201-2003ffff 81070202-0701ffff
81070201-2003ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (DIMM 3
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702012003ffff or 0x810702012003ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
81070201-2004ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (DIMM 4
Temp)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702012004ffff or 0x810702012004ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
81070202-0701ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (SysBrd Vol
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702020701ffff or 0x810702020701ffff
Severity: Info
Alert Category: Critical - Voltage
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 1
Automatically notify Support: No
User response: No action; information only.
338
81070204-0a01ffff 81070208-0a01ffff
81070204-0a01ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 1 Fan
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702040a01ffff or 0x810702040a01ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
81070204-0a02ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 2 Fan
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702040a02ffff or 0x810702040a02ffff
Severity: Info
Alert Category: Critical - Fan Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 11
Automatically notify Support: No
User response: No action; information only.
81070208-0a01ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 1 Therm
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702080a01ffff or 0x810702080a01ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
339
81070208-0a02ffff 81070301-0301ffff
81070208-0a02ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 2 Therm
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702080a02ffff or 0x810702080a02ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
81070219-0701ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (SysBrd
Fault)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
May also be shown as 810702190701ffff or 0x810702190701ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0523
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 810703010301ffff or 0x810703010301ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0525
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
340
81070608-0a01ffff 810b0108-1301ffff
81070608-0a01ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable. (PS 1 VCO
Fault)
Explanation: This message is for the use case when an implementation has detected that the Sensor transition to
non-recoverable has deasserted.
May also be shown as 810706080a01ffff or 0x810706080a01ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0531
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only. PS1 12V OC Fault : PS1 12V OV Fault : PS1 12V UV Fault :
81070608-0a02ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable. (PS 2 VCO
Fault)
Explanation: This message is for the use case when an implementation has detected that the Sensor transition to
non-recoverable has deasserted.
May also be shown as 810706080a02ffff or 0x810706080a02ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0531
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only. PS2 12V OC Fault : PS2 12V OV Fault : PS2 12V UV Fault :
810b0108-1301ffff
Explanation: This message is for the use case when Redundacy Lost has deasserted.
May also be shown as 810b01081301ffff or 0x810b01081301ffff
Severity: Info
Alert Category: Critical - Redundant Power Supply
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0803
SNMP Trap ID: 9
Automatically notify Support: No
User response: No action; information only.
341
816f0008-0a01ffff 816f0009-1301ffff
816f0008-0a01ffff [PowerSupplyElementName] has been removed from container
[PhysicalPackageElementName]. (Power Supply 1)
Explanation: This message is for the use case when an implementation has detected a Power Supply has been
removed.
May also be shown as 816f00080a01ffff or 0x816f00080a01ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0085
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f0008-0a02ffff [PowerSupplyElementName] has been removed from container
[PhysicalPackageElementName]. (Power Supply 2)
Explanation: This message is for the use case when an implementation has detected a Power Supply has been
removed.
May also be shown as 816f00080a02ffff or 0x816f00080a02ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0085
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f0009-1301ffff
Explanation: This message is for the use case when an implementation has detected a Power Unit that has been
Enabled.
May also be shown as 816f00091301ffff or 0x816f00091301ffff
Severity: Info
Alert Category: System - Power On
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0107
SNMP Trap ID: 24
Automatically notify Support: No
User response: No action; information only.
342
816f000d-0400ffff 816f000d-0401ffff
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.
May also be shown as 816f000d0400ffff or 0x816f000d0400ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0163
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Reseat hard disk drive n.(n = hard disk drive number). Wait 1 minute or more before reinstalling the drive.
2.
Make sure that the disk firmware and RAID controller and backplane firmware are at the latest level.
3.
4.
Reseat hard disk drive n.(n = hard disk drive number). Wait 1 minute or more before reinstalling the drive.
2.
Make sure that the disk firmware and RAID controller and backplane firmware are at the latest level.
3.
4.
343
816f000d-0402ffff 816f000d-0403ffff
816f000d-0402ffff The Drive [StorageVolumeElementName] has been removed from unit
[PhysicalPackageElementName]. (Drive 2)
Explanation: This message is for the use case when an implementation has detected a Drive has been Removed.
May also be shown as 816f000d0402ffff or 0x816f000d0402ffff
Severity: Error
Alert Category: Critical - Hard Disk drive
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0163
SNMP Trap ID: 5
Automatically notify Support: No
User response:
1.
Reseat hard disk drive n.(n = hard disk drive number). Wait 1 minute or more before reinstalling the drive.
2.
Make sure that the disk firmware and RAID controller and backplane firmware are at the latest level.
3.
4.
Reseat hard disk drive n.(n = hard disk drive number). Wait 1 minute or more before reinstalling the drive.
2.
Make sure that the disk firmware and RAID controller and backplane firmware are at the latest level.
3.
4.
344
816f000f-2201ffff 816f0021-2582ffff
816f000f-2201ffff The System [ComputerSystemElementName] has detected a POST Error deassertion. (ABR
Status)
Explanation: This message is for the use case when an implementation has detected that Post Error has deasserted.
May also be shown as 816f000f2201ffff or 0x816f000f2201ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0185
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only. Firmware Error :
816f0013-1701ffff
Explanation: This message is for the use case when an implementation has detected a recovery from a Front Panel
NMI / Diagnostic Interrupt
May also be shown as 816f00131701ffff or 0x816f00131701ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0223
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
816f0021-2582ffff Fault condition removed on slot [PhysicalConnectorElementName] on system
[ComputerSystemElementName]. (All PCI Error)
Explanation: This message is for the use case when an implementation has detected a Fault condition in a slot has
been removed.
May also be shown as 816f00212582ffff or 0x816f00212582ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0331
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only. One of PCI Error :
345
816f0021-3001ffff 816f0108-0a01ffff
816f0021-3001ffff Fault condition removed on slot [PhysicalConnectorElementName] on system
[ComputerSystemElementName]. (PCI 1)
Explanation: This message is for the use case when an implementation has detected a Fault condition in a slot has
been removed.
May also be shown as 816f00213001ffff or 0x816f00213001ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0331
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only. PCI 2 :
816f0107-0301ffff
Explanation: This message is for the use case when an implementation has detected a Over-Temperature Condition
has been Removed for Processor.
May also be shown as 816f01070301ffff or 0x816f01070301ffff
Severity: Info
Alert Category: Critical - Temperature
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0037
SNMP Trap ID: 0
Automatically notify Support: No
User response: No action; information only.
816f0108-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply return to
normal operational status.
May also be shown as 816f01080a01ffff or 0x816f01080a01ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0087
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
346
816f0108-0a02ffff 816f010c-2002ffff
816f0108-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply return to
normal operational status.
May also be shown as 816f01080a02ffff or 0x816f01080a02ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0087
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
816f010c-2001ffff Uncorrectable error recovery 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
recovery.
May also be shown as 816f010c2001ffff or 0x816f010c2001ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0139
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f010c-2002ffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 2)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
May also be shown as 816f010c2002ffff or 0x816f010c2002ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0139
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
347
816f010c-2003ffff 816f010c-2581ffff
816f010c-2003ffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
May also be shown as 816f010c2003ffff or 0x816f010c2003ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0139
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f010c-2004ffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 4)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
May also be shown as 816f010c2004ffff or 0x816f010c2004ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0139
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f010c-2581ffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (All DIMMS)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
May also be shown as 816f010c2581ffff or 0x816f010c2581ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0139
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only. One of the DIMMs :
348
816f010d-0400ffff 816f010d-0402ffff
816f010d-0400ffff
Explanation: This message is for the use case when an implementation has detected a Drive was Enabled.
May also be shown as 816f010d0400ffff or 0x816f010d0400ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0167
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f010d-0401ffff
Explanation: This message is for the use case when an implementation has detected a Drive was Enabled.
May also be shown as 816f010d0401ffff or 0x816f010d0401ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0167
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f010d-0402ffff
Explanation: This message is for the use case when an implementation has detected a Drive was Enabled.
May also be shown as 816f010d0402ffff or 0x816f010d0402ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0167
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
349
816f010d-0403ffff 816f0125-1d01ffff
816f010d-0403ffff
Explanation: This message is for the use case when an implementation has detected a Drive was Enabled.
May also be shown as 816f010d0403ffff or 0x816f010d0403ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0167
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 816f010f2201ffff or 0x816f010f2201ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0187
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
816f0125-1d01ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is now
Present.
May also be shown as 816f01251d01ffff or 0x816f01251d01ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0390
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
350
816f0125-1d02ffff 816f0125-1d04ffff
816f0125-1d02ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is now
Present.
May also be shown as 816f01251d02ffff or 0x816f01251d02ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0390
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f0125-1d03ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is now
Present.
May also be shown as 816f01251d03ffff or 0x816f01251d03ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0390
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f0125-1d04ffff
Explanation: This message is for the use case when an implementation has detected a Managed Element is now
Present.
May also be shown as 816f01251d04ffff or 0x816f01251d04ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0390
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
351
816f0207-0301ffff 816f020d-0401ffff
816f0207-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor Recovered FRB1/BIST condition.
May also be shown as 816f02070301ffff or 0x816f02070301ffff
Severity: Info
Alert Category: Critical - CPU
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0045
SNMP Trap ID: 40
Automatically notify Support: No
User response: No action; information only.
816f020d-0400ffff Failure no longer 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 no longer
Predicted.
May also be shown as 816f020d0400ffff or 0x816f020d0400ffff
Severity: Info
Alert Category: System - Predicted Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0169
SNMP Trap ID: 27
Automatically notify Support: No
User response: No action; information only.
816f020d-0401ffff Failure no longer Predicted on drive [StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive 1)
Explanation: This message is for the use case when an implementation has detected an Array Failure is no longer
Predicted.
May also be shown as 816f020d0401ffff or 0x816f020d0401ffff
Severity: Info
Alert Category: System - Predicted Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0169
SNMP Trap ID: 27
Automatically notify Support: No
User response: No action; information only.
352
816f020d-0402ffff 816f0308-0a01ffff
816f020d-0402ffff Failure no longer Predicted on drive [StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive 2)
Explanation: This message is for the use case when an implementation has detected an Array Failure is no longer
Predicted.
May also be shown as 816f020d0402ffff or 0x816f020d0402ffff
Severity: Info
Alert Category: System - Predicted Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0169
SNMP Trap ID: 27
Automatically notify Support: No
User response: No action; information only.
816f020d-0403ffff Failure no longer Predicted on drive [StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive 3)
Explanation: This message is for the use case when an implementation has detected an Array Failure is no longer
Predicted.
May also be shown as 816f020d0403ffff or 0x816f020d0403ffff
Severity: Info
Alert Category: System - Predicted Failure
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0169
SNMP Trap ID: 27
Automatically notify Support: No
User response: No action; information only.
816f0308-0a01ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply that has input
that has returned to normal.
May also be shown as 816f03080a01ffff or 0x816f03080a01ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0099
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
353
816f0308-0a02ffff 816f030c-2002ffff
816f0308-0a02ffff
Explanation: This message is for the use case when an implementation has detected a Power Supply that has input
that has returned to normal.
May also be shown as 816f03080a02ffff or 0x816f03080a02ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0099
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 816f030c2001ffff or 0x816f030c2001ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0137
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f030c-2002ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has
recovered. (DIMM 2)
Explanation: This message is for the use case when an implementation has detected a Memory Scrub failure
recovery.
May also be shown as 816f030c2002ffff or 0x816f030c2002ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0137
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
354
816f030c-2003ffff 816f0313-1701ffff
816f030c-2003ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has
recovered. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory Scrub failure
recovery.
May also be shown as 816f030c2003ffff or 0x816f030c2003ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0137
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f030c-2004ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has
recovered. (DIMM 4)
Explanation: This message is for the use case when an implementation has detected a Memory Scrub failure
recovery.
May also be shown as 816f030c2004ffff or 0x816f030c2004ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0137
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f0313-1701ffff
Explanation: This message is for the use case when an implementation has detected a Software NMI has been
Recovered from.
May also be shown as 816f03131701ffff or 0x816f03131701ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0230
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
355
816f040c-2001ffff 816f040c-2003ffff
816f040c-2001ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
May also be shown as 816f040c2001ffff or 0x816f040c2001ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0130
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f040c-2002ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
May also be shown as 816f040c2002ffff or 0x816f040c2002ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0130
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f040c-2003ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
May also be shown as 816f040c2003ffff or 0x816f040c2003ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0130
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
356
816f040c-2004ffff 816f0413-2582ffff
816f040c-2004ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
May also be shown as 816f040c2004ffff or 0x816f040c2004ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0130
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f040c-2581ffff
Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
May also be shown as 816f040c2581ffff or 0x816f040c2581ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0130
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only. One of the DIMMs :
816f0413-2582ffff
Explanation: This message is for the use case when an implementation has detected a PCI PERR recovered.
May also be shown as 816f04132582ffff or 0x816f04132582ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0233
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
357
816f0507-0301ffff 816f050c-2002ffff
816f0507-0301ffff
Explanation: This message is for the use case when an implementation has Recovered from a Processor
Configuration Mismatch.
May also be shown as 816f05070301ffff or 0x816f05070301ffff
Severity: Info
Alert Category: Critical - CPU
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0063
SNMP Trap ID: 40
Automatically notify Support: No
User response: No action; information only.
816f050c-2001ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Removed.
May also be shown as 816f050c2001ffff or 0x816f050c2001ffff
Severity: Info
Alert Category: Warning - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0145
SNMP Trap ID: 43
Automatically notify Support: No
User response: No action; information only.
816f050c-2002ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 2)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Removed.
May also be shown as 816f050c2002ffff or 0x816f050c2002ffff
Severity: Info
Alert Category: Warning - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0145
SNMP Trap ID: 43
Automatically notify Support: No
User response: No action; information only.
358
816f050c-2003ffff 816f050c-2581ffff
816f050c-2003ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Removed.
May also be shown as 816f050c2003ffff or 0x816f050c2003ffff
Severity: Info
Alert Category: Warning - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0145
SNMP Trap ID: 43
Automatically notify Support: No
User response: No action; information only.
816f050c-2004ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 4)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Removed.
May also be shown as 816f050c2004ffff or 0x816f050c2004ffff
Severity: Info
Alert Category: Warning - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0145
SNMP Trap ID: 43
Automatically notify Support: No
User response: No action; information only.
816f050c-2581ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (All DIMMS)
Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Removed.
May also be shown as 816f050c2581ffff or 0x816f050c2581ffff
Severity: Info
Alert Category: Warning - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0145
SNMP Trap ID: 43
Automatically notify Support: No
User response: No action; information only. One of the DIMMs :
359
816f050d-0400ffff 816f050d-0402ffff
816f050d-0400ffff
Explanation: This message is for the use case when an implementation has detected that an Critiacal Array has
deasserted.
May also be shown as 816f050d0400ffff or 0x816f050d0400ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0175
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f050d-0401ffff
Explanation: This message is for the use case when an implementation has detected that an Critiacal Array has
deasserted.
May also be shown as 816f050d0401ffff or 0x816f050d0401ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0175
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f050d-0402ffff
Explanation: This message is for the use case when an implementation has detected that an Critiacal Array has
deasserted.
May also be shown as 816f050d0402ffff or 0x816f050d0402ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0175
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
360
816f050d-0403ffff 816f0608-0a01ffff
816f050d-0403ffff
Explanation: This message is for the use case when an implementation has detected that an Critiacal Array has
deasserted.
May also be shown as 816f050d0403ffff or 0x816f050d0403ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0175
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 816f06070301ffff or 0x816f06070301ffff
Severity: Info
Alert Category: Critical - CPU
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0817
SNMP Trap ID: 40
Automatically notify Support: No
User response: No action; information only.
816f0608-0a01ffff
Explanation: This message is for the use case when an implementation when a Power Supply configuration is OK.
May also be shown as 816f06080a01ffff or 0x816f06080a01ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0105
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
361
816f0608-0a02ffff 816f060d-0401ffff
816f0608-0a02ffff
Explanation: This message is for the use case when an implementation when a Power Supply configuration is OK.
May also be shown as 816f06080a02ffff or 0x816f06080a02ffff
Severity: Info
Alert Category: Critical - Power
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0105
SNMP Trap ID: 4
Automatically notify Support: No
User response: No action; information only.
816f060d-0400ffff
Explanation: This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
May also be shown as 816f060d0400ffff or 0x816f060d0400ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0177
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f060d-0401ffff
Explanation: This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
May also be shown as 816f060d0401ffff or 0x816f060d0401ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0177
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
362
816f060d-0402ffff 816f070c-2001ffff
816f060d-0402ffff
Explanation: This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
May also be shown as 816f060d0402ffff or 0x816f060d0402ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0177
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f060d-0403ffff
Explanation: This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
May also be shown as 816f060d0403ffff or 0x816f060d0403ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0177
SNMP Trap ID: 5
Automatically notify Support: No
User response: No action; information only.
816f070c-2001ffff Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has deasserted.
May also be shown as 816f070c2001ffff or 0x816f070c2001ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0127
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
363
816f070c-2002ffff 816f070c-2004ffff
816f070c-2002ffff Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (DIMM 2)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has deasserted.
May also be shown as 816f070c2002ffff or 0x816f070c2002ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0127
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f070c-2003ffff Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (DIMM 3)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has deasserted.
May also be shown as 816f070c2003ffff or 0x816f070c2003ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0127
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
816f070c-2004ffff Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (DIMM 4)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has deasserted.
May also be shown as 816f070c2004ffff or 0x816f070c2004ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0127
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only.
364
816f070c-2581ffff 816f070d-0401ffff
816f070c-2581ffff Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (All DIMMS)
Explanation: This message is for the use case when an implementation has detected a Memory DIMM configuration
error has deasserted.
May also be shown as 816f070c2581ffff or 0x816f070c2581ffff
Severity: Info
Alert Category: Critical - Memory
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0127
SNMP Trap ID: 41
Automatically notify Support: No
User response: No action; information only. One of the DIMMs :
816f070d-0400ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
May also be shown as 816f070d0400ffff or 0x816f070d0400ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0179
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f070d-0401ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
May also be shown as 816f070d0401ffff or 0x816f070d0401ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0179
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
365
816f070d-0402ffff 816f0807-0301ffff
816f070d-0402ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
May also be shown as 816f070d0402ffff or 0x816f070d0402ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0179
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f070d-0403ffff
Explanation: This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
May also be shown as 816f070d0403ffff or 0x816f070d0403ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0179
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
816f0807-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor has been Enabled.
May also be shown as 816f08070301ffff or 0x816f08070301ffff
Severity: Info
Alert Category: System - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0060
SNMP Trap ID:
Automatically notify Support: No
User response: No action; information only.
366
816f0813-0301ffff 816f0813-2582ffff
816f0813-0301ffff
Explanation: This message is for the use case when an implementation has detected a that a system has recovered
from a Bus Uncorrectable Error.
May also be shown as 816f08130301ffff or 0x816f08130301ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0241
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
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.
May also be shown as 816f08132581ffff or 0x816f08132581ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0241
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
816f0813-2582ffff
Explanation: This message is for the use case when an implementation has detected a that a system has recovered
from a Bus Uncorrectable Error.
May also be shown as 816f08132582ffff or 0x816f08132582ffff
Severity: Info
Alert Category: Critical - Other
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0241
SNMP Trap ID: 50
Automatically notify Support: No
User response: No action; information only.
367
816f0a07-0301ffff
816f0a07-0301ffff
Explanation: This message is for the use case when an implementation has detected a Processor is no longer
running in the Degraded state.
May also be shown as 816f0a070301ffff or 0x816f0a070301ffff
Severity: Info
Alert Category: Warning - CPU
Serviceable: No
CIM Information: Prefix: PLAT and ID: 0039
SNMP Trap ID: 42
Automatically notify Support: No
User response: No action; information only.
368
Description
Informational
Warning
Error
User response
Indicate the actions that you should take to resolve the event.
Perform the steps listed in this section in the order shown until the
problem is solved. After you perform all of the actions that are described
in this field, if you cannot solve the problem, contact IBM support.
The following is the list of the UEFI (POST) error codes and suggested actions to
correct the detected problems.
369
I.11002 I.18007
I.11002
[I.11002] A processor mismatch has been detected between one or more processors in the system.
This message could occur with messages about other Processor configuration problems. Resolve those messages
first.
If the problem persists, ensure that matching processors are installed (i.e., matching option part numbers, etc)
2.
3.
Verify that the Processors are installed in the correct sockets according to the service information for this
product. If not, correct that problem.
4.
Check IBM support site for an applicable service bulletin or firmware update that applies to this Processor error.
5.
(Trained Service technician only) Replace mismatching processor. Inspect Processor socket and replace the system
board first if socket is damaged.
I.1100A
Check IBM support site for an applicable service bulletin or firmware update that applies to this Processor error.
2.
I.18005
[I.18005] A discrepancy has been detected in the number of cores reported by one or more processor
packages within the system.
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.
Check IBM support site for an applicable service bulletin that applies to this Processor error.
2.
3.
(Trained Service technician only) Replace Processor. Inspect Processor socket and replace the system board first if
socket is damaged.
I.18007
[I.18007] A power segment mismatch has been detected for one or more processor packages.
2.
Ensure that all Processors have matching power requirements (such as 65, 95, or 130 Watts)
3.
If power requirements match, check IBM support site for an applicable service bulletin or firmware update that
applies to this Processor error.
4.
(Trained Service technician only) Replace Processor. Inspect Processor socket and replace the system board first if
socket is damaged
370
I.18008 I.1800C
I.18008
Verify that matching DIMMs are installed in the correct population sequence, according to the service
information for this product. 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.
Verify that matching processors are installed in the correct processor sockets according to the service information
for this product. Correct any mismatch issues found.
2.
Check IBM support site for an applicable service bulletin or firmware update 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.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
User response: Complete the following steps:
1.
Verify that matching processors are installed in the correct processor sockets according to the service information
for this product. Correct any mismatch found.
2.
Check IBM support site for an applicable service bulletin or firmware update that applies to this Processor error.
3.
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
User response: Complete the following steps:
1.
Verify 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 or firmware update that applies to this Processor error.
3.
371
I.1800D I.18010
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
User response: Complete the following steps:
1.
Verify 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 or firmware update that applies to this Processor error.
3.
I.1800E
[I.1800E] A processor model mismatch has been detected for one or more processor packages.
Verify 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 or firmware update that applies to this Processor error.
3.
I.1800F
[I.1800F] A processor family mismatch has been detected for one or more processor packages.
Verify 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 or firmware update that applies to this Processor error.
3.
I.18010
[I.18010] A processor stepping mismatch has been detected for one or more processor packages.
Verify 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 or firmware update that applies to this Processor error.
3.
372
I.2018002 I.3818003
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 %.
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.
4.
Move card to a different slot. If slot not available or error re-occurs, replace adapter.
(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.3818001
[I.3818001] The firmware image capsule signature for the currently booted flash bank is invalid.
Reboot system. Will come up on backup UEFI image. Reflash the primary UEFI image.
2.
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.
2.
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.
373
I.58015 S.1100B
I.58015
No user required for this event. This is for informational purposes only.
I.580A4
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.
Check the system-event log for uncorrected DIMM failures and replace those DIMMs.
I.580A6
Check system log for related DIMM failures and replace those DIMMs.
S.1100B
Check IBM support site for an applicable service bulletin or firmware update that applies to this Processor error.
2.
374
S.1100C S.2011001
S.1100C
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
S.2011000
[S.2011000] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID
for the device is % and the Device ID is %.
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.
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 %.
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.
375
S.2018001 S.3040007
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 %.
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.
S.3020007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
S.3030007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
S.3040007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
376
S.3050007 S.3818004
S.3050007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
S.3060007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
S.3070007
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
2.
3.
S.3818004
[S.3818004] The CRTM flash driver could not successfully flash the staging area. A failure occurred.
Continue booting sytem. If system does not reset, manually reset the system.
2.
If the error is not reported on the subsequent boot, no additional recovery action is required.
3.
If the error persists, continue booting system and reflash UEFI image.
4.
377
S.3818007 S.51006
S.3818007
[S.3818007] The firmware image capsules for both flash banks could not be verified.
1.
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.
If system fails to boot, or if flash attempt fails, (Trained service technician only) Replace the system board.
3.
S.51003
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
User response: Complete the following steps:
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.
7.
S.51006
[S.51006] A memory mismatch has been detected. Please verify that the memory configuration is
valid.
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.
5.
Replace DIMM
6.
378
S.51009 S.58008
S.51009
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.
5.
S.5100A
[S.5100A] Memory is present within the system but could not be configured. Please verify that the
memory configuration is valid.
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.
Reseat all DIMMs ensuring that DIMMs are installed in the correct population sequence, according to the service
information for this product.
4.
Clear CMOS memory. Note that all firmware settings will revert to the defaults.
5.
6.
7.
S.58008
3.
4.
You must AC-cycle the system to re-enable affected DIMM connector or re-enable manually using F1 setup
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.)
If problem persists, replace the DIMM identified by LightPath and/or event log entry.
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
Processors, swap Processors to move affected Procesor to another Processor socket and retry. If problem follows
the affected Processor (or there is only one Processor), replace the affected Processor.
8.
379
S.68005 W.3818005
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.
1.
2.
Check IBM support site for an applicable service bulletin or firmware update for the system or adapter that
applies to this error.
(Trained Service technician only) Replace the system board.
3.
W.11004
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 Processors, swap Processors to move affected Processor to
another Processor socket and retry. If problem follows the affected Processor, or this is a single Processor system,
replace the Processor. Inspect Processor socket on each Processor removal and replace system board first if
damaged or mis-aligned pins are found.
3.
W.3818000
[W.3818005] The CRTM flash driver could not successfully flash the staging area. The update was
aborted
Continue booting system. If system does not reset, manually reset the system.
2.
If the error is not reported on the subsequent boot, no additional recovery action is required.
3.
If the event persists, continue booting system and reflash UEFI image.
4.
380
W.50001 W.58001
W.50001
[W.50001] A DIMM has been disabled due to an error detected during POST.
If the DIMM was disabled because of a memory fault, follow the procedure for that event.
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.
4.
5.
6.
7.
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 %.
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.
9.
381
W.58007 W.68002
W.58007
[W.58007] Invalid memory configuration (Unsupported DIMM Population) detected. Please verify
memory configuration is valid.
1.
W.580A1
[W.580A1] Invalid memory configuration for Mirror Mode. Please correct memory configuration.
1.
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.
Make sure that the DIMM connectors are correctly populated for sparing mode, according to the service
information for this product.
W.580A3
[W.580A3] Invalid memory configuration for Lock-Step Mode. Please correct memory configuration.
Make sure that the DIMM connectors are correctly populated for lock-step mode, according to the service
information for this product.
W.68002
If the system was recently Installed, Moved, or Serviced, makesure the batter is properly seated.
2.
Check IBM support site for an applicable service bulletin or firmware update that applies to this error.
3.
4.
382
405-001-000
383
405-002-000 405-004-000
405-002-000
405-003-000
405-004-000
384
405-005-000 405-007-000
405-005-000
405-006-000
405-007-000
385
405-800-000 405-802-000
405-800-000
405-801-000
405-802-000
386
405-803-000 405-805-000
405-803-000
405-804-000
405-805-000
387
405-806-000 405-900-000
405-806-000
405-807-000
405-900-000
388
405-901-000 405-902-000
405-901-000
405-902-000
389
405-903-000 405-904-000
405-903-000
405-904-000
390
405-905-000 405-906-000
405-905-000
405-906-000
Explanation: A failure was detected during the loopback test at the physical layer.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
391
405-907-000 218-000-000
405-907-000
Explanation: A failure was detected while verifying operation of the status LEDs.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
Brocade:MemoryTest Passed
392
218-001-000 218-003-000
218-001-000
Brocade:ExternalLoopbackTest Passed
218-002-000
Brocade:SerdesLoopbackTest Passed
218-003-000
Brocade:PCILoopbackTest Passed
393
218-004-000 218-006-000
218-004-000
Brocade:ExternalEthLoopbackTest Passed
218-005-000
Brocade:SerdesEthLoopbackTest Passed
218-006-000
Brocade:InternalLoopbackTest Passed
394
218-800-000 218-802-000
218-800-000
Brocade:MemoryTest Aborted
218-801-000
Brocade:ExternalLoopbackTest Aborted
218-802-000
Brocade:SerdesLoopbackTest Aborted
395
218-803-000 218-805-000
218-803-000
Brocade:PCILoopbackTest Aborted
218-804-000
Brocade:ExternalEthLoopbackTest Aborted
218-805-000
Brocade:SerdesEthLoopbackTest Aborted
396
218-806-000 218-901-000
218-806-000
Brocade:InternalLoopbackTest Aborted
218-900-000
Brocade:MemoryTest Failed
218-901-000
Brocade:ExternalLoopbackTest Failed
397
218-902-000 218-903-000
218-902-000
Brocade:SerdesLoopbackTest Failed
218-903-000
Brocade:PCILoopbackTest Failed
398
218-904-000 218-905-000
218-904-000
Brocade:ExternalEthLoopbackTest Failed
218-905-000
Brocade:SerdesEthLoopbackTest Failed
399
218-906-000 180-801-000
218-906-000
Brocade:InternalLoopbackTest Failed
180-801-000
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
Automatically notify Support: No
User response: Complete the following steps:
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.
4. If failure remains, refer to "Troubleshooting by symptom" in the system "Installation and Service Guide" for the
next corrective action.
400
180-901-000 089-000-000
Related Links:
v
180-901-000
401
089-801-000 089-802-000
089-801-000
089-802-000
402
089-803-000 089-901-000
089-803-000
Explanation: CPU Stress Test Aborted. Memory size is insufficient to run the test. At least 1GB is required.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
Related Links:
v
089-804-000
089-901-000
403
516-000-000 516-002-000
516-001-000
516-002-000
404
516-800-000 516-802-000
516-800-000
516-801-000
516-802-000
405
516-900-000 516-901-000
516-900-000
Explanation: A failure was detected during the loopback test at the MAC layer.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
516-901-000
Explanation: A failure was detected during the loopback test at the physical layer.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
406
516-902-000 401-000-000
516-902-000
Explanation: A failure was detected while verifying operation of the status LEDs.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
407
401-801-000 401-802-000
401-801-000
Explanation: EXA Port Ping Test Aborted. Unable to get device base address.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
401-802-000
Explanation: EXA Port Ping Test Aborted. Port connections may not be correct.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
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:
v
408
401-901-001 217-000-000
401-901-001
409
217-800-000 217-900-000
217-800-000
217-900-000
Explanation: HDD Test Failed. The hard drive self-test detected a failure.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Check cable connections.
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:
v
410
406-000-000 406-002-000
406-001-000
406-002-000
411
406-003-000 406-800-000
406-003-000
406-004-000
406-800-000
412
406-801-000 406-803-000
406-801-000
406-802-000
406-803-000
413
406-804-000 406-901-000
406-804-000
406-900-000
406-901-000
414
406-902-000 406-903-000
406-902-000
406-903-000
415
406-904-000 407-000-000
406-904-000
416
407-800-000 407-900-000
407-800-000
407-900-000
417
408-000-000 408-800-000
408-000-000
408-001-000
408-800-000
418
408-801-000 408-901-000
408-801-000
408-900-000
408-901-000
419
201-000-000 201-000-002
201-000-001
201-000-002
420
201-000-003 201-811-000
201-000-003
201-000-004
201-811-000
421
201-811-001 201-811-002
201-811-001
201-811-002
422
201-811-003 201-812-000
201-811-003
201-812-000
423
201-812-001 201-812-002
201-812-001
201-812-002
424
201-812-003 201-813-000
201-812-003
201-813-000
Explanation: Chipset Error: Can not turn OFF ECC error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
425
201-813-001 201-813-002
201-813-001
Explanation: Chipset Error: Can not turn OFF ECC error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-813-002
Explanation: Chipset Error: Can not turn OFF ECC error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
426
201-813-003 201-814-000
201-813-003
Explanation: Chipset Error: Can not turn OFF ECC error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-814-000
Explanation: Chipset Error: Can not disable Scubbing feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
427
201-814-001 201-814-002
201-814-001
Explanation: Chipset Error: Can not disable Scubbing feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-814-002
Explanation: Chipset Error: Can not disable Scubbing feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
428
201-814-003 201-815-000
201-814-003
Explanation: Chipset Error: Can not disable Scubbing feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-815-000
429
201-815-001 201-815-002
201-815-001
201-815-002
430
201-815-003 201-816-000
201-815-003
201-816-000
431
201-816-001 201-816-002
201-816-001
201-816-002
432
201-816-003 201-818-000
201-816-003
201-818-000
433
201-818-001 201-818-002
201-818-001
201-818-002
434
201-818-003 201-819-000
201-818-003
201-819-000
Explanation: The start-end address ranges in the restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
435
201-819-001 201-819-002
201-819-001
Explanation: The start-end address ranges in the restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-819-002
Explanation: The start-end address ranges in the restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
436
201-819-003 201-820-000
201-819-003
Explanation: The start-end address ranges in the restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-820-000
437
201-820-001 201-820-002
201-820-001
201-820-002
438
201-820-003 201-821-000
201-820-003
201-821-000
Explanation: Variable range MTRR registers are larger than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
439
201-821-001 201-821-002
201-821-001
Explanation: Variable range MTRR registers are larger than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-821-002
Explanation: Variable range MTRR registers are larger than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
440
201-821-003 201-822-000
201-821-003
Explanation: Variable range MTRR registers are larger than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-822-000
441
201-822-001 201-822-002
201-822-001
201-822-002
442
201-822-003 201-824-000
201-822-003
201-824-000
Explanation: Node Interleave feature must be OFF. Go to Setup and disable Node Interleave option and then re-run
the test.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
443
201-824-001 201-824-002
201-824-001
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
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-824-002
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
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
444
201-824-003 201-826-000
201-824-003
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
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-826-000
Explanation: BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
445
201-826-001 201-826-002
201-826-001
Explanation: BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-826-002
Explanation: BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
446
201-826-003 201-827-000
201-826-003
Explanation: BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-827-000
Explanation: BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
447
201-827-001 201-827-002
201-827-001
Explanation: BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-827-002
Explanation: BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
448
201-827-003 201-844-000
201-827-003
Explanation: BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-844-000
Explanation: Chipset Error: Problem in masking MSR machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
449
201-844-001 201-844-002
201-844-001
Explanation: Chipset Error: Problem in masking MSR machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-844-002
Explanation: Chipset Error: Problem in masking MSR machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
450
201-844-003 201-845-000
201-844-003
Explanation: Chipset Error: Problem in masking MSR machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-845-000
Explanation: Chipset Error: Problem clearing MSR machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
451
201-845-001 201-845-002
201-845-001
Explanation: Chipset Error: Problem clearing MSR machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-845-002
Explanation: Chipset Error: Problem clearing MSR machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
452
201-845-003 201-859-000
201-845-003
Explanation: Chipset Error: Problem clearing MSR machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-859-000
453
201-859-001 201-859-002
201-859-001
201-859-002
454
201-859-003 201-860-000
201-859-003
201-860-000
455
201-860-001 201-860-002
201-860-001
201-860-002
456
201-860-003 201-861-000
201-860-003
201-861-000
457
201-861-001 201-861-002
201-861-001
201-861-002
458
201-861-003 201-862-000
201-861-003
201-862-000
459
201-862-001 201-862-002
201-862-001
201-862-002
460
201-862-003 201-863-000
201-862-003
201-863-000
461
201-863-001 201-863-002
201-863-001
201-863-002
462
201-863-003 201-864-000
201-863-003
201-864-000
463
201-864-001 201-864-002
201-864-001
201-864-002
464
201-864-003 201-865-000
201-864-003
201-865-000
465
201-865-001 201-865-002
201-865-001
201-865-002
466
201-865-003 201-866-000
201-865-003
201-866-000
467
201-866-001 201-866-002
201-866-001
201-866-002
468
201-866-003 201-867-000
201-866-003
201-867-000
469
201-867-001 201-867-002
201-867-001
201-867-002
470
201-867-003 201-868-000
201-867-003
201-868-000
471
201-868-001 201-868-002
201-868-001
201-868-002
472
201-868-003 201-869-000
201-868-003
201-869-000
473
201-869-001 201-869-002
201-869-001
201-869-002
474
201-869-003 201-870-000
201-869-003
201-870-000
475
201-870-001 201-870-002
201-870-001
201-870-002
476
201-870-003 201-871-000
201-870-003
201-871-000
477
201-871-001 201-871-002
201-871-001
201-871-002
478
201-871-003 201-877-000
201-871-003
201-877-000
Explanation: BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
479
201-877-001 201-877-002
201-877-001
Explanation: BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-877-002
Explanation: BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
480
201-877-003 201-878-000
201-877-003
Explanation: BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-878-000
Explanation: Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
481
201-878-001 201-878-002
201-878-001
Explanation: Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-878-002
Explanation: Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
482
201-878-003 201-885-000
201-878-003
Explanation: Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-885-000
Explanation: Processor does not support MTRR register manipulation. Can not write to memory without cache.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
483
201-885-001 201-885-002
201-885-001
Explanation: Processor does not support MTRR register manipulation. Can not write to memory without cache.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-885-002
Explanation: Processor does not support MTRR register manipulation. Can not write to memory without cache.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
484
201-885-003 201-886-000
201-885-003
Explanation: Processor does not support MTRR register manipulation. Can not write to memory without cache.
Severity: Warning
Serviceable: No
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Perform the actions mentioned one at a time and try the test after each action.
2. If the problem remains, contact your technical-service representative.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s). Reconnect it to power.
4. Make sure that DSA and BIOS/uEFI are at the latest level.
Related Links:
v
201-886-000
485
201-886-001 201-886-002
201-886-001
201-886-002
486
201-886-003 201-899-001
201-886-003
201-899-000
201-899-001
487
201-899-002 201-901-000
201-899-002
201-899-003
201-901-000
488
201-901-001 201-901-002
201-901-001
201-901-002
489
201-901-003 202-000-000
201-901-003
490
202-801-000 202-802-000
202-801-000
202-802-000
491
202-803-000 202-901-000
202-803-000
202-901-000
492
202-902-000 409-000-000
202-902-000
493
409-003-000 409-005-000
409-003-000
409-004-000
409-005-000
494
409-006-000 409-803-000
409-006-000
409-800-000
409-803-000
495
409-804-000 409-806-000
409-804-000
409-805-000
409-806-000
496
409-900-000 409-903-000
409-900-000
409-903-000
497
409-904-000 409-905-000
409-904-000
409-905-000
498
409-906-000 215-000-000
409-906-000
499
215-801-000 215-802-000
215-801-000
215-802-000
500
215-803-000 215-804-000
215-803-000
Explanation: Optical Drive Test Failed. Disk may be in use by the operating system.
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Wait for the system activity to cease
2. Run the test again
3. Turn off and restart the system.
4. Run the test again.
Related Links:
v
215-804-000
501
215-901-000 215-902-000
215-901-000
215-902-000
502
215-903-000 166-000-001
215-903-000
Explanation: Optical Drive Test Aborted. Could not access the device.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: No
User response: Complete the following steps:
1. Insert a new CD or DVD into the drive and wait for 15 seconds for the media to be recognized. Rerun the test.
2. Check the drive cabling for loose or broken connections at both ends or damage to the cable. Replace the cable if
damage is present.
3. Run the test again.
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.
5. Run the test again.
6. If failure remains, refer to "Troubleshooting by symptom" in the system "Installation and Service Guide" for the
next corrective action.
Related Links:
v
503
166-801-001 166-803-001
166-801-001
166-802-001
166-803-001
504
166-804-001 166-806-001
166-804-001
166-805-001
166-806-001
505
166-807-001 166-809-001
166-807-001
166-808-001
166-809-001
506
166-810-001 166-812-001
166-810-001
166-811-001
166-812-001
507
166-813-001 166-815-001
166-813-001
166-814-001
166-815-001
508
166-816-001 166-818-001
166-816-001
166-817-001
166-818-001
509
166-819-001 166-821-001
166-819-001
Explanation: Command response could not be provided. SDR Repository in?update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: 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:
v
166-820-001
Explanation: Command response could not be provided. Device in firmware update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
Automatically notify Support: 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:
v
166-821-001
510
166-822-001 166-824-001
166-822-001
166-823-001
166-824-001
511
166-901-001 166-903-001
166-901-001
166-903-001
512
166-907-001 264-000-000
166-907-001
Explanation: IMM Indicates failure in the Temperature Sensor bus (BUS 6).
Severity: Error
Serviceable: Yes
Recoverable: No
Automatically notify Support: 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.
3. Run the test again.
4. If failure remains, refer to "Troubleshooting by symptom" in the system "Installation and Service Guide" for the
next corrective action.
Related Links:
v
513
264-901-000 264-902-000
264-901-000
264-902-000
514
264-903-000 264-904-000
264-903-000
264-904-000
515
264-905-000 264-906-000
264-905-000
264-906-000
516
264-907-000 264-908-000
264-907-000
264-908-000
517
518
519
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.
520
521
522
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.
523
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
524
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 37. 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
Notices
525
Limits
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.
526
Notices
527
528
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
529
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.
530
Notices
531
532
Index
Numerics
240 VA safety cover
remove 210
replacing 212
A
ABR, automatic boot recovery 137
ac power LED 16
accessible documentation 526
Active Energy Manager plug-in 9
adapter, install 56
adapter, remove 156
adapter, replace 157
administrator
password 79
air baffle, remove 42, 152
air baffle, replace 64, 153
applying current firmware
using best practices 21
ASM event log 9, 110
assertion event, system-event log 109
assistance, getting 519
attention notices 5
Australia Class A statement 527
automatic boot recovery (ABR) 137
availability, server 12
B
backup firmware
starting 80
battery
remove 183
replace 185
bays 6
before you install a legacy operating
system 73
best practices
use to apply current firmware and
device-driver updates 21
bezel, remove 150
bezel, replace 151
blue screen capture features 9
blue-screen capture feature
overview 9, 83
blue-screen feature 83
Boot Manager 80
Boot Manager program 70
Business Partners instructions 21, 22
C
cable, connection 66
cache 6
call home feature
IBM Electronic Service Agent
call home tools 115
D
116
danger statements 5
data collection 97
dc power LED 16
deassertion event, system-event log
device drivers 81
devices
installing 21
devices, static-sensitive
handling guidelines 40
diagnostic
on-board programs, starting 114
tools, overview 102
diagnostics
program overview 112
diagnostics program
DSA Preboot 9
dimensions 6
dimm
install 51, 176
unbuffered 31, 53, 177
DIMM, install 54, 178
DIMMs
removal 175
display problems 123
documentation
Documentation Browser 3
format 526
System x Documentation CD 3
using 520
documentation cd 3
documentation, updated
finding 4
drive 6
drives
installation rules 32, 45
DSA 22
edition 113
program, overview 112
test log, viewing 115
text message format 115
DSA data
how to send to IBM 22
DSA log 9, 109, 110
DSA Portable 102, 113
DSA Preboot 102, 113
DSA Preboot diagnostic program 9
DSA, sending data to IBM 520
DVD
drive activity LED 14
drive DVD LED 14
eject button 14
DVD drive
install 35
problems 120
DVD drive cable
remove 191
replace 192
DVD drive, install 49
DVD drive, remove 170
DVD drive, replace 172
Dynamic System Analysis 22
Dynamic System Analysis (DSA) Preboot
diagnostics program 9
109
533
E
electrical equipment, servicing x
electrical input 6
electronic emission Class A notice 527
embedded hypervisor
using 86
enabling
Features on Demand
Ethernet software 87
RAID software 87
environment 6
error codes and messages
IMM2 229
UEFI (POST) 369
error messages 116
error messages, IMM2 229
error symptoms 123
DVD drive 120
general 117
hard disk drive 117
intermittent 121
keyboard 121
memory 122
microprocessor 123
monitor 123
mouse 121
network connection 126
optional devices 126
power 127
serial port 128
ServerGuide 129
software 130
USB port 131
USB-device 121
errors
format, DSA code 115
Ethernet 9, 16
controller 132
link status LED 16
Ethernet activity
LED 16
Ethernet connector 16
Ethernet controller configuration 70
Ethernet controller, configure 87
Ethernet support 9
European Union EMC Directive
conformance statement 528
event log 109
viewing 110
event log, POST 109
event log, system 109
event logs
clearing 111
event logs, methods for viewing 110
events, IMM2 229
expansion
bays 6
external connectors 25
F
fan
simple-swap 6
fan, install 44
fan, remove 180
fan, replace 181
534
fans 9
FCC Class A notice 527
features 6
ServerGuide 72
features, remote presence and
blue-screen 9
finding
updated documentation 4
firmware updates 1, 38
firmware updates best practices 21
firmware, server, recovering 135
firmware, updating 69
fixed power supply
remove 206
fixed power supply, replace 208
front view
connectors 14
LED location 14
front view of the server 14
G
gaseous contamination 6, 525
general
problems 117
Germany Class A statement 528
grease, thermal 222
guidelines
options installation 38
servicing electrical equipment x
system reliability 39
trained service technicians ix
H
handling static-sensitive devices 40
hard disk drive
activity LED 14
problems 117
status LED 14
hardware requirements 3
hardware service and support telephone
numbers 521
hardware, configuring 70
head output 6
heat sink, remove 217
heat sink, replace 219
help
from the World Wide Web 520
from World Wide Web 520
sending diagnostic data to IBM 520
sources of 519
hot-swap drive
installing 34
hot-swap drive backplane
removing 195, 203
hot-swap hard disk drive
remove 167
replace 168
hot-swap hard disk drive, install 46
hot-swap power supply
remove 187
hot-swap power supply, install 61
hot-swap power supply, replace 188
how to send DSA data to IBM 22
humidity 6
I
IBM Advanced Settings Utility program
overview 88
IBM Electronic Service Agent 116
IBM Systems Director 9
systems management tool 13
updating 88
IBM Taiwan product service 521
IBM, next generation technology 9
IMM host name 84
IMM web interface 85
IMM2 70
IMM2 error messages 229
IMM2 events 229
IMM2 heartbeat
LED 108
important notices 5, 524
in-band
automated boot recovery
method 137
manual recovery method 135
information center 520
inspecting for unsafe conditions ix
install
DVD drive 35
installation 1
installation guidelines 38
installing
adapter 56
dimm 51, 176
DIMM 54, 178
drives 32, 45
DVD drive 49
fan 44
hot-swap drive 34
hot-swap hard disk drive 46
hot-swap power supply 61
memory 51, 176
memory module 30
ServeRAID adapter 58
simple-swap drives 33
simple-swap hard disk drive 47
installing options 21
instructions for IBM Business
Partners 21, 22
integrated baseboard management
controller 18
integrated functions 6
integrated management module
event log 9
overview 9
using 82
integrated management module II
event log 109, 110
programs 70
intermittent
problems 121
internal connectors 25
internal, system board connectors 25
introduction 1
IP address for the IMM 84
IPMI event log 9, 109, 110
IPMItool 110
J
Japan Class A electronic emission
statement 529
Japan Electronics and Information
Technology Industries Association
statement 530
JEITA statement 530
jumper
UEFI boot recovery 135
jumpers
system board 26
K
Korea Class A electronic emission
statement 530
L
LED
ac power 16
dc power 16
DVD drive activity 14
Ethernet activity 16
Ethernet-link status 16
hard disk drive activity 14
hard disk drive status 14
IMM2 heartbeat 108
power supply error 16
RTMM heartbeat 108
system pulse 108
LEDs
front of server 14
light path diagnotics
power-supply 104, 106
on the system board 28
power-supply 104, 106
power-supply detected
problems 104, 106
legacy operating system
requirement 73
local area network (LAN) 9
locator LED 14
logging 85
M
management, system 9
memory 6, 9
install 51, 176
UDIMM 51, 176
unbuffered 31, 53, 177
memory module
installing 30
removing 175
memory support 9
menu choices
Setup utility 74
messages, error
POST 369
method 137
methods, viewing event logs
microprocessor 9
problems 123
specifications 6
110
model name
location 134
N
New Zealand Class A statement
next generation technology 9
NMI button 16
noise emissions 6
NOS installation
with ServerGuide 73
without ServerGuide 73
notes 5
notes, important 524
notices 523
electronic emission 527
FCC, Class A 527
notices and statements 5
Nx-boot failure 138
527
O
obtaining 84
online documentation 1
online publications 4
operating system 3
operating-system event log 9, 109, 110
operator information panel
assembly, removing 193
assembly, replacing 194
optional device problems 126
options
installing 21
options installation, completing 63
out-of-band 137
P
particulate contamination 6, 525
parts listing 139
password 78
administrator 78
power-on 78
password, power-on
switch on system board 79
PCI
slot 1 16
slot 2 16
PCI expansion
slots 6
PCI riser-card assembly
connectors 29
PCI riser-card assembly 29
PCI riser-card assembly, remove 43, 154
People's Republic of China Class A
electronic emission statement 530
policy option 81
POST
error codes 369
event log 110
POST event log 109
POST, intro 112
power 81
power-control button 14
requirement 6
power cords 144
power features
of the server 17
power on and working inside the
server 40
power paddle card, remove 214
power paddle card, replace 215
power problems 127, 131
power supplies
redundancy support 9
power supply 6
power-control button 14
power-on LED 17
power-on self-test 112
power-supply
LEDs 104, 106
LEDs and detected problems 104,
106
power-supply LEDs 104, 106
Preboot, DSA diagnostics program 9
problems 123
DVD drive 120
Ethernet controller 132
general 117
hard disk drive 117
intermittent 121
keyboard 121
memory 122
microprocessor 123
monitor 123
mouse 121
network connection 126
optional devices 126
power 127, 131
serial port 128
ServerGuide 129
software 130
undetermined 133
USB port 131
procedure, checkout 101
product service, IBM Taiwan 521
R
RAID arrays
configuring 87
RAS features, server 12
rear view 16
of the server 16
recovering the server firmware 135
redundancy support
power supplies 9
redundant 9
cooling 9
Ethernet connection 9
Redundant
Ethernet capabilities 12
hot-swap power supplies 12
reliability, server 12
remote presence feature
using 83
removing
240 VA safety cover 210
adapter 156
air baffle 42, 152
battery 183
bezel 150
components 147
Index
535
removing (continued)
cover 41, 148
DVD drive 170
DVD drive cable 191
fan 180
fixed power supply 206
heat sink 217
hot-swap drive backplane 195, 203
hot-swap hard disk drive 167
hot-swap power supply 187
memory modules 175
operator information panel
assembly 193
PCI riser-card assembly 43, 154
power paddle card 214
second microprocessor 217
server components 147
ServeRAID adapter 160
simple-swap drive backplate
assembly 195, 203
simple-swap hard disk drive 164
system board 223
Tier 1 CRUs 148
removing and replacing
removing
structural parts 206
server components 147
structural parts 206
Tier 1 CRUs 148
removing, DIMMs 175
Replaceable server components 139
replacing
240 VA safety cover 212
adapter 157
air baffle 64, 153
battery 185
bezel 151
components 147
cover 65, 149
DVD drive 172
DVD drive cable 192
fan 181
fixed power supply 208
heat sink 219
hot-swap hard disk drive 168
hot-swap power supply 188
operator information panel
assembly 194
power paddle card 215
second microprocessor 219
server components 147
ServeRAID adapter 161
simple-swap drive backplate
assembly 196, 204
simple-swap hard disk drive 165
software RAID simple-swap hard disk
drive backplate with hardware
RAID simple-swap hard disk drive
backplate 197
structural parts 206
system board 225
the PCI riser-card assembly 63, 155
Tier 1 CRUs 148
Tier 2 CRUs 190
requirements
hardware 3
software 3
536
reset button 14
returning
component 147
device 147
RTMM heartbeat
LED 108
Russia Class A electronic emission
statement 530
S
safety vii
Safety Information 5
safety statements vii, xi
second microprocessor, remove 217
second microprocessor, replace 219
sending diagnostic data to IBM 520
sending DSA data
to IBM 22
serial connector 16
serial number
location 134
serial port problems 128
server
offerings 9
power features 17
turn off 18
turn on 17
working inside with the power
on 40
server , backup firmware
starting 80
server components 23, 139
server configuration, updating 68
server controls, LEDs, and power 14
server firmware, recovering 135
server rear view 16
server shutdown 18
server, front view 14
ServeRAID adapter, install 58
ServeRAID adapter, remove 160
ServeRAID adapter, replace 161
ServeRAID support 9
ServerGuide
features 72
NOS installation 73
setup 73
Setup and Installation CD 69
using 72
ServerGuide CD 9
serverproven 38
service and support
before you call 519
hardware 521
software 521
service bulletins 100
serviceability, server 12
servicing electrical equipment x
Setup utility 69, 70
menu choices 74
starting 74
using 74
shutting down the server 18
simple-swap drive backplate assembly
hot-swap drive backplane
replacing 196, 204
removing 195, 203
T
Taiwan Class A electronic emission
statement 531
telecommunication regulatory
statement 526
telephone numbers 521
temperature 6
test log, viewing 115
the PCI riser-card assembly, replace
155
63,
W
Wake on LAN feature 17
weight 6
what the server offers 9
working inside with the power on
ix
40
X
x3250
introduction
U
UDIMM
considereations 31, 53, 177
requirement 31, 51, 53, 176, 177
UEFI
boot recovery jumper 135
error codes 369
unbuffered
dimm 31, 53, 177
memory 31, 53, 177
Unbuffered DIMM 31, 51, 53, 176, 177
undetermined problems 133
undocumented problems 99
United States FCC Class A notice 527
Universal Serial Bus (USB) problems 131
unsafe conditions, inspecting for ix
UpdateXpress 69, 81
updating
firmware 69
IBM Systems Director 88
server configuration 68
Systems Director, IBM 88
Universal Unique Identifier
(UUID) 90, 92
USB
connector 14, 16
using
embedded hypervisor 86
integrated management module 82
Setup utility 74
the remote presence feature 83
using best practices
to apply firmware and device-driver
updates 21
Utility program
IBM Advanced Settings 88
utility, Setup 70
starting 74
using 74
V
video connector
rear 16
video controller, integrated
specifications 6
viewing event log 110
Index
537
538
Printed in USA