PDF 3633 Isg

Lenovo System x3250 M6
Installation and Service Guide
Machine Types: 3633 and 3943

Note
Before using this information and the product it supports, read the general information in Appendix D
“Getting help and technical assistance” on page 589, Appendix E “Notices” on page 593, the safety
information, warranties, and licenses information on the Lenovo Web site at:
https://support.lenovo.com/documents/LNVO-DOCS
Eighth Edition (July 2018)
© Copyright Lenovo 2016, 2018.

LIMITED AND RESTRICTED RIGHTS NOTICE: If data or software is delivered pursuant to a General Services
Administration (GSA) contract, use, reproduction, or disclosure is subject to restrictions set forth in Contract No. GS-35F-
05925.
Contents
Safety . . . . . . . . . . . . . . . . . . v Accessing RAID configuration utility . . . . . 39

Guidelines for trained service technicians . . . . . . vi Lenovo XClarity Essentials OneCLI . . . . . 39
Inspecting for unsafe conditions . . . . . . . vi Using Lenovo XClarity Administrator . . . . . 39
Guidelines for servicing electrical equipment. . . vii Updating the Universal Unique Identifier
Safety statements . . . . . . . . . . . . . . viii (UUID). . . . . . . . . . . . . . . . . 40
Updating the DMI/SMBIOS data . . . . . . 41
Chapter 1. Documentation and Configuring onboard SATA software RAID . . . . 43
notice types . . . . . . . . . . . . . . . 1 Enabling the onboard SATA RAID
Related documentation . . . . . . . . . . . . . 1 functionality . . . . . . . . . . . . . . 43
Notices in this document . . . . . . . . . . . . 1 Creating RAID volumes . . . . . . . . . . 44
Deleting RAID volumes . . . . . . . . . . 44
Chapter 2. About the Lenovo System Marking disks as spare . . . . . . . . . . 44
x3250 M6 server . . . . . . . . . . . . . 3
Server features and specifications . . . . . . . . 4 Chapter 5. Troubleshooting . . . . . . 47
What your server offers . . . . . . . . . . . . . 8 Start here . . . . . . . . . . . . . . . . . 47
Reliability, Availability, and Serviceability . . . . . 11 Diagnosing a problem . . . . . . . . . . 47
Turning on or turning off the server . . . . . . . 12 Opening an online service request . . . . . . 49
Turning on the server . . . . . . . . . . . 12 Service bulletins . . . . . . . . . . . . . . 49
Turning off the server . . . . . . . . . . . 12 Checkout procedure . . . . . . . . . . . . . 50
Precautions before performing the checkout
Chapter 3. Component locations . . . 15 procedure . . . . . . . . . . . . . . . 50
Front view . . . . . . . . . . . . . . . . . 15 Performing the checkout procedure . . . . . 50
Rear view . . . . . . . . . . . . . . . . . 17 Diagnostic tools. . . . . . . . . . . . . . . 51
Operator information panel . . . . . . . . . . 18 Light path diagnostics . . . . . . . . . . 53
Server components . . . . . . . . . . . . . 19 Error LEDs . . . . . . . . . . . . . . . 53
System-board connectors. . . . . . . . . . . 21 Power-supply LEDs . . . . . . . . . . . 54
System-board switches and jumpers . . . . . . 21 System pulse LEDs . . . . . . . . . . . 55
System-board LEDs . . . . . . . . . . . . . 23 Event logs . . . . . . . . . . . . . . . 56
POST . . . . . . . . . . . . . . . . . 58
Chapter 4. Configuration Dynamic System Analysis . . . . . . . . . 58
information . . . . . . . . . . . . . . . 25 Automated service request (call home) . . . . . . 60
Updating the firmware . . . . . . . . . . . . 25 Electronic Service Agent . . . . . . . . . 60
Configuring the server . . . . . . . . . . . . 26 Error messages . . . . . . . . . . . . . . . 60
Using the ServerGuide Setup and Installation Troubleshooting by symptom . . . . . . . . . 61
CD . . . . . . . . . . . . . . . . . . 27 General problems . . . . . . . . . . . . 61
Using the Setup Utility program . . . . . . . 29 Optical drive problems . . . . . . . . . . 62
Using the Boot Manager program . . . . . . 34 Hard disk drive problems . . . . . . . . . 62
Starting the backup server firmware . . . . . 34 Hypervisor problems . . . . . . . . . . . 64
Changing the Power Policy option to the Intermittent problems . . . . . . . . . . . 65
default settings after loading UEFI defaults . . 34
Keyboard, mouse, or USB-device problems . . 65
Using the Integrated Management Module 2.1
(IMM2.1) . . . . . . . . . . . . . . . . 35 Memory problems . . . . . . . . . . . . 65
Using the remote presence and blue-screen Monitor problems . . . . . . . . . . . . 67
capture features . . . . . . . . . . . . . 36 Network connection problems . . . . . . . 68
Using the embedded hypervisor . . . . . . 38 Optional-device problems . . . . . . . . . 69
Ethernet controller information . . . . . . . 38 Operating system boot problem . . . . . . 69
Enabling Features on Demand Ethernet and Power problems . . . . . . . . . . . . . 70
Demand RAID software . . . . . . . . . . 38 Serial port problems . . . . . . . . . . . 71
© Copyright Lenovo 2016, 2018 i

ServerGuide problems . . . . . . . . . . 71 Test results for the DSA Broadcom network
Software problems . . . . . . . . . . . . 72 test . . . . . . . . . . . . . . . . . . 451
USB connector problems . . . . . . . . . 72 DSA Brocade test results . . . . . . . . . . . 460
Chipset driver installation problems . . . . . 72 Test results for the DSA Brocade test . . . . 460
Solving power problems . . . . . . . . . . . 72 DSA checkpoint panel test results . . . . . . . 468
Solving Ethernet controller problems . . . . . . 73 Test results for the DSA checkpoint panel
test . . . . . . . . . . . . . . . . . . 468
Solving undetermined problems . . . . . . . . 74
DSA CPU stress test results . . . . . . . . . . 469
Problem determination tips . . . . . . . . . . 74
Test results for the DSA CPU stress test . . . 469
Recovering the server firmware (UEFI update
failure) . . . . . . . . . . . . . . . . . . 76 DSA Emulex adapter test results . . . . . . . . 472
In-band manual recovery method . . . . . . 76 Test results for the DSA Emulex adapter
test . . . . . . . . . . . . . . . . . . 472
In-band automated boot recovery method . . 77
DSA EXA port ping test results . . . . . . . . . 475
Out-of-band method . . . . . . . . . . . 77
Test results for the DSA EXA port ping test . . 475
Automated boot recovery (ABR) . . . . . . . . 77
DSA hard drive test results . . . . . . . . . . 477
Nx-boot failure . . . . . . . . . . . . . . . 77
Test results for the DSA hard drive test . . . . 477
Chapter 6. Parts listing, Lenovo DSA Intel network test results . . . . . . . . . 479
System x3250 M6 . . . . . . . . . . . 79 Test results for the DSA Intel network test . . . 479
Replaceable server components . . . . . . . . 79 DSA LSI hard drive test results . . . . . . . . . 484
Structural parts . . . . . . . . . . . . . 90 Test results for the DSA LSI hard drive test . . 485
Power cords . . . . . . . . . . . . . . . . 90 DSA Mellanox adapter test results . . . . . . . 486
Test results for the DSA Mellanox adapter
Chapter 7. Removing and installing test . . . . . . . . . . . . . . . . . . 486
server components . . . . . . . . . . 93 DSA memory isolation test results. . . . . . . . 488
Before removing or installing server Test results for the DSA memory isolation
components . . . . . . . . . . . . . . . . 93 test . . . . . . . . . . . . . . . . . . 488
System reliability guidelines . . . . . . . . 93 DSA memory stress test results . . . . . . . . 557
Working inside the server with the power on . . 93 Test results for the DSA memory stress
test . . . . . . . . . . . . . . . . . . 557
Handling static-sensitive devices . . . . . . 94
DSA Nvidia GPU test results . . . . . . . . . . 559
Removing and installing server components. . . . 94
Test results for the DSA Nvidia GPU test . . . 559
Removing and installing structural parts . . . 94
DSA optical drive test results . . . . . . . . . 565
Removing and installing Tier 1 CRUs . . . . . 101
Test results for the DSA optical drive test . . . 565
Removing and installing Tier 2 CRUs . . . . . 145
DSA system management test results . . . . . . 569
Internal cable routing . . . . . . . . . . . 157
Test results for the DSA system management
Completing the parts replacement. . . . . . 170
test . . . . . . . . . . . . . . . . . . 570
Instructions for Business Partners . . . . . . 171
DSA tape drive test results . . . . . . . . . . 584
Sending DSA data to Lenovo . . . . . . . . 171
Test results for the DSA tape drive test . . . . 584
Returning a device or component . . . . . . 171
Appendix D. Getting help and
Appendix A. Integrated Management technical assistance . . . . . . . . . . 589
Module 2.1 (IMM2.1) error Before you call . . . . . . . . . . . . . . . 589
messages . . . . . . . . . . . . . . . 173 Using the documentation . . . . . . . . . . . 590
IMM Events that automatically notify Support . . . 174
Getting help and information from the World Wide
List of IMM events . . . . . . . . . . . . . . 177 Web . . . . . . . . . . . . . . . . . . . 590
How to send DSA data . . . . . . . . . . . . 590
Appendix B. UEFI (POST) error Creating a personalized support web page . . . . 590
codes. . . . . . . . . . . . . . . . . . 441 Software service and support . . . . . . . . . 591
List of UEFI events. . . . . . . . . . . . . . 441
Hardware service and support . . . . . . . . . 591
Appendix C. DSA diagnostic test Taiwan product service . . . . . . . . . . . . 591
results . . . . . . . . . . . . . . . . . 451 Appendix E. Notices . . . . . . . . . . 593
DSA Broadcom network test results . . . . . . . 451
ii Lenovo System x3250 M6 Installation and Service Guide

Trademarks . . . . . . . . . . . . . . . . 594 European Union EMC Directive conformance
Important notes . . . . . . . . . . . . . . . 594 statement . . . . . . . . . . . . . . . 596
Recycling information . . . . . . . . . . . . 594 Germany Class A statement . . . . . . . . 597
Particulate contamination . . . . . . . . . . . 595 Japanese electromagnetic compatibility
statements . . . . . . . . . . . . . . . 598
Telecommunication regulatory statement . . . . . 595
Korea Communications Commission (KCC)
Electronic emission notices . . . . . . . . . . 595 statement . . . . . . . . . . . . . . . 598
Federal Communications Commission (FCC) Russia Electromagnetic Interference (EMI)
statement . . . . . . . . . . . . . . . 596 Class A statement . . . . . . . . . . . . 599
Industry Canada Class A emission compliance People's Republic of China Class A electronic
statement . . . . . . . . . . . . . . . 596 emission statement . . . . . . . . . . . 599
Avis de conformité à la réglementation Taiwan Class A compliance statement . . . . 599
d'Industrie Canada. . . . . . . . . . . . 596
Taiwan BSMI RoHS declaration . . . . . . . 600
Australia and New Zealand Class A
statement . . . . . . . . . . . . . . . 596
Index . . . . . . . . . . . . . . . . . . 601
© Copyright Lenovo 2016, 2018 iii

iv Lenovo System x3250 M6 Installation and Service Guide
Safety
Before installing this product, read the Safety Information.
Antes de instalar este produto, leia as Informações de Segurança.
Læs sikkerhedsforskrifterne, før du installerer dette produkt.
Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.
Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information.
Avant d'installer ce produit, lisez les consignes de sécurité.
Vor der Installation dieses Produkts die Sicherheitshinweise lesen.
Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.
Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.
Antes de instalar este produto, leia as Informações sobre Segurança.
© Copyright Lenovo 2016, 2018 v

Antes de instalar este producto, lea la información de seguridad.
Läs säkerhetsinformationen innan du installerar den här produkten.
Guidelines for trained service technicians

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

Use this information to help you identify potential unsafe conditions in a device that you are working on.
Each device, as it was designed and manufactured, has required safety items to protect users and service
technicians from injury. The information in this section addresses only those items. Use good judgment to
identify potential unsafe conditions that might be caused by unsupported alterations or attachment of
unsupported features or optional devices that are not addressed in this section. If you identify an unsafe
condition, you must determine how serious the hazard is and whether you must correct the problem before
you work on the product.
Consider the following conditions and the safety hazards that they present:
• Electrical hazards, especially primary power. Primary voltage on the frame can cause serious or fatal
electrical shock.
• Explosive hazards, such as a damaged CRT face or a bulging capacitor.
• Mechanical hazards, such as loose or missing hardware.
To inspect the product for potential unsafe conditions, complete the following steps:
1. Make sure that the power is off and the power cords are disconnected.
2. Make sure that the exterior cover is not damaged, loose, or broken, and observe any sharp edges.
3. Check the power cords:
• Make sure that the third-wire ground connector is in good condition. Use a meter to measure third-
wire ground continuity for 0.1 ohm or less between the external ground pin and the frame ground.
• Make sure that the power cords are the correct type.
• Make sure that the insulation is not frayed or worn.
4. Remove the cover.
vi Lenovo System x3250 M6 Installation and Service Guide

5. Check for any obvious unsupported alterations. Use good judgment as to the safety of any unsupported
alterations.
6. Check inside the system for any obvious unsafe conditions, such as metal filings, contamination, water
or other liquid, or signs of fire or smoke damage.
7. Check for worn, frayed, or pinched cables.
8. Make sure that the power-supply cover fasteners (screws or rivets) have not been removed or tampered
with.
Guidelines for servicing electrical equipment

Observe these guidelines when you service electrical equipment.
• Check the area for electrical hazards such as moist floors, nongrounded power extension cords, and
missing safety grounds.
• Use only approved tools and test equipment. Some hand tools have handles that are covered with a soft
material that does not provide insulation from live electrical current.
• Regularly inspect and maintain your electrical hand tools for safe operational condition. Do not use worn
or broken tools or testers.
• Do not touch the reflective surface of a dental mirror to a live electrical circuit. The surface is conductive
and can cause personal injury or equipment damage if it touches a live electrical circuit.
• Some rubber floor mats contain small conductive fibers to decrease electrostatic discharge. Do not use
this type of mat to protect yourself from electrical shock.
• Do not work alone under hazardous conditions or near equipment that has hazardous voltages.
• Locate the emergency power-off (EPO) switch, disconnecting switch, or electrical outlet so that you can
turn off the power quickly in the event of an electrical accident.
• Disconnect all power before you perform a mechanical inspection, work near power supplies, or remove
or install main units.
• Before you work on the equipment, disconnect the power cord. If you cannot disconnect the power cord,
have the customer power-off the wall box that supplies power to the equipment and lock the wall box in
the off position.
• Never assume that power has been disconnected from a circuit. Check it to make sure that it has been
disconnected.
• If you have to work on equipment that has exposed electrical circuits, observe the following precautions:
– Make sure that another person who is familiar with the power-off controls is near you and is available to
turn off the power if necessary.
– When you work with powered-on electrical equipment, use only one hand. Keep the other hand in your
pocket or behind your back to avoid creating a complete circuit that could cause an electrical shock.
– When you use a tester, set the controls correctly and use the approved probe leads and accessories for
that tester.
– Stand on a suitable rubber mat to insulate you from grounds such as metal floor strips and equipment
frames.
• Use extreme care when you measure high voltages.
• To ensure proper grounding of components such as power supplies, pumps, blowers, fans, and motor
generators, do not service these components outside of their normal operating locations.
• If an electrical accident occurs, use caution, turn off the power, and send another person to get medical
aid.
© Copyright Lenovo 2016, 2018 vii

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:

• Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration
of this product during an electrical storm.
• Connect all power cords to a properly wired and grounded electrical outlet.
• Connect to properly wired outlets any equipment that will be attached to this product.
• When possible, use one hand only to connect or disconnect signal cables.
• Never turn on any equipment when there is evidence of fire, water, or structural damage.
• 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.
• Connect and disconnect cables as described in the following table when installing, moving, or
opening covers on this product or attached devices.
To Connect: To Disconnect:
1. Turn everything OFF. 1. Turn everything OFF.

2. First, attach all cables to devices. 2. First, remove power cords from outlet.
3. Attach signal cables to connectors. 3. Remove signal cables from connectors.
4. Attach power cords to outlet. 4. Remove all cables from devices.
5. Turn device ON.
viii Lenovo System x3250 M6 Installation and Service Guide

Statement 2
CAUTION:
When replacing the lithium battery, use only Part Number 33F8354 or an equivalent type battery
recommended by the manufacturer. If your system has a module containing a lithium battery, replace
it only with the same module type made by the same manufacturer. The battery contains lithium and
can explode if not properly used, handled, or disposed of. Do not:
• Throw or immerse into water
• Heat to more than 100°C (212°F)
• Repair or disassemble
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:
• 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.
• 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.
© Copyright Lenovo 2016, 2018 ix

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.
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
x Lenovo System x3250 M6 Installation and Service Guide

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.
DO NOT open up the chassis or any other parts of any UPS unit. This will void the unit warranty. Only
replace parts for which a serviceable part exists, that is servicing any UPS unit is limited to FRU / CRU
replacement parts.
Statement 12
CAUTION:
The following label indicates a hot surface nearby.
Statement 26
CAUTION:
Do not place any object on top of rack-mounted devices.
Statement 27
© Copyright Lenovo 2016, 2018 xi

CAUTION:
Hazardous moving parts are nearby.
Rack Safety Information, Statement 2
DANGER
• Always lower the leveling pads on the rack cabinet.

• Always install stabilizer brackets on the rack cabinet.
• Always install servers and optional devices starting from the bottom of the rack cabinet.
• Always install the heaviest devices in the bottom of the rack cabinet.
C004
CAUTION:
Lead-acid batteries can present a risk of electrical burn from high, short-circuit current. Avoid battery
contact with metal materials; remove watches, rings, or other metal objects, and use tools with
insulated handles. To avoid possible explosion, do not burn.
Exchange only with the Lenovo-approved part. Recycle or discard the battery as instructed by local
regulations. In the United States, Lenovo has a process for the collection of this battery. For
information, call 1-800-426-4333. Have the Lenovo part number for the battery unit available when you
call.
DO NOT mix old and new batteries in an Uninterruptible Power Supply unit.
DO NOT open up any battery pack retrieved from an Uninterruptible Power Supply unit.
Wear safety goggles for your own protection when replacing batteries of an Uninterruptible Power
Supply unit. (C004)
xii Lenovo System x3250 M6 Installation and Service Guide

Chapter 1. Documentation and notice types
This topic provides general descriptions of the various documentation and notices for your server and
instructions on how to obtain all the documentation.
Related documentation
Refer to the documentation in this topic to help you use and maintain your server.
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 most recent version of the
Installation and Service Guide is always available at:
http://publib.boulder.ibm.com/infocenter/ systemx/documentation/index.jsp
For safety information, warranties, licenses, and product documentation, go to:

https://support.lenovo.com/documents/LNVO-DOCS
For warranty lookup (type, duration, status), go to:

http://www.lenovo.com/warranty
The Lenovo XClarity Essentials (LXCE) is an online information center that contains information about tools
for updating, managing, and deploying firmware, device drivers, and operating systems. The Lenovo XClarity
Essentials (LXCE) is at http://sysmgt.lenovofiles.com/help/index.jsp.
The server might have features that are not described in the documentation that you received with the server.
The documentation might be updated occasionally to include information about those features, or technical
updates might be available to provide additional information that is not included in the server documentation.
These updates are available from the Lenovo website. To check for updates, go to http://www.lenovo.com/
support.
Notices in this document

The caution and danger statements in this document are also in the multilingual Safety Information
document, which is available at https://support.lenovo.com/documents/LNVO-DOCS. Each statement is
numbered for reference to the corresponding statement in your language in the Safety Information
document.
The following notices and notices are used in this document:
• Note: These notices provide important tips, guidance, or advice.

• Important: These notices provide information or advice that might help you avoid inconvenient or
problem situations.
• Attention: These notices indicate potential damage to programs, devices, or data. An attention notice is
placed just before the instruction or situation in which damage might occur.
• CAUTION: These notices indicate situations that can be potentially hazardous to you. A caution notice is
placed just before the description of a potentially hazardous procedure, step, or situation.
• DANGER: These notices indicate situations that can be potentially lethal or extremely hazardous to you. A
danger notice is placed just before the description of a potentially lethal or extremely hazardous
procedure, step, or situation.
© Copyright Lenovo 2016, 2018 1

2 Lenovo System x3250 M6 Installation and Service Guide
Chapter 2. About the Lenovo System x3250 M6 server
This chapter provides a summary of server features, technologies the server offers, and instructions on
turning on and turning off the server.
General information
The Lenovo System x3250 M6 server is a 1-U1-high rack model server for high-volume network transaction
processing. This high-performance, multi-core server is ideally suited for networking environments that
require superior microprocessor performance, input/output (I/O) flexibility, and high manageability.
The hot-swap server models support up to eight 2.5-inch hot-swap hard disk drives or four 3.5-inch hot-
swap hard disk drives. The simple-swap server models support up to eight 2.5-inch simple-swap hard disk
drives or four 3.5-inch simple-swap hard disk drives. The Lenovo System x3250 M6 server supports 2.5-inch
hot-swap or simple-swap Serial Attached SCSI (SAS) or SATA hard disk drives, or 3.5-inch hot-swap SAS or
SATA hard disk drives, or 3.5-inch simple-swap SATA hard disk drives.
For a list of supported optional devices for the server, go to:

http://www.lenovo.com/ serverproven/
Record information about the server in the following table.
Table 1. Record of the system information
Product name Machine types Model number Serial number

Lenovo System x3250 M6 Type 3633 and 3943
server
The model number and serial number are on the ID label on the rack release latch of the server, as shown in
the following illustration.
Figure 1. ID label on the front of the server
The MAC address label is on the top side of the user information tag, as shown in the following illustration.
Note: The illustrations in this document might differ slightly from your hardware.
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

Figure 2. MAC address label
Performance, ease of use, reliability, and expansion capabilities were key considerations in the design of the
server. These design features make it possible for you to customize the system hardware to meet your needs
today and provide flexible expansion capabilities for the future.
Business Partners must also complete the steps in “Instructions for Business Partners” on page 171.
Warranty and service information

The server comes with a limited warranty. For information about the terms of the warranty and getting service
and assistance, see the Lenovo Warranty Information document that comes with the server.
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 Lenovo Service Information Web site. The Lenovo Service Information Web site
provides additional information for parts installation and replacement videos, and error codes for server
support.
If firmware and documentation updates are available, you can download them from the Lenovo Web site. The
server might have features that are not described in the documentation that comes with the server, and the
documentation might be updated occasionally to include information about those features, or technical
updates might be available to provide additional information that is not included in the server documentation.
To check for updates, go to http://www.lenovo.com/support.
You can obtain up-to-date information about the server and other Lenovo server products at http://
shop.lenovo.com/us/ en/systems/. At http://www.lenovo.com/support, you can create a personalized support
page by identifying Lenovo products that are of interest to you. From this personalized page, you can
subscribe to weekly email notifications about new technical documents, search for information and
downloads, and access various administrative services.
Technologies and software information

The server contains X-Architecture next generation technologies, which help increase performance and
reliability. For more information, see “What your server offers” on page 8 and “Reliability, Availability, and
Serviceability” on page 11.
If you participate in the Lenovo client reference program, you can share information about your use of
technology, best practices, and innovative solutions; build a professional network; and gain visibility for your
business. For more information about the Lenovo client reference program, go to http://www.ibm.com/ibm/
clientreference/.
Server features and specifications

The following information is a summary of the server features and specifications. Depending on the model,
some features might not be available, or some specifications might vary.
Microprocessor (depending on the model):

• One Intel® quad-core (Xeon® E3-1200 v5 or v6 series) or dual-core (Pentium® series, Celeron® series,
or Core™ i3 series) microprocessor
• Multi-chip package microprocessor architecture
• Designed for Land Grid Array (LGA) 1151 socket
• Scalable up to four cores
• Support Intel Flex Memory Technology
Notes: For the following microprocessors, the frequency will be reduced slightly if the C h o o s e
O p e r a t i n g M o d e is set as E f f i c i e n c y - F a v o r P e r f o r m a n c e in BIOS. It is an expected behavior for Intel
thermal design power (TDP) feature. If you want the microprocessor to run at its maximum frequency,
set the C h o o s e O p e r a t i n g M o d e to be M a x i m u m P e r f o r m a n c e in BIOS.
• Intel Core-i3 7300T
• Intel Core-i3 7100T
• Intel Pentium G4600T
• Intel Pentium G4560T
• Intel Celeron G3930T
For the specific type and speed of the server microprocessor, view the information in the Setup Utility
program. See “Using the Setup Utility program” on page 29.
For a list of supported microprocessors, go to:

Memory:
• Minimum: 4 GB
• Maximum: 64 GB
• Types: PC4-17000 (dual-rank), 2133 MHz or 2400 MHz, error correcting code (ECC), double-data-
rate 4 (DDR4) unbuffered dual inline memory modules (DIMMs) only
• Slots: four DIMM slots, two-way interleaved
Notes:
• If your server comes with 2400 MHz memory modules and a microprocessor that supports a
maximum of 2133 MHz memory, the data rate of your memory modules will be limited to 2133 MHz.
• If you mix memory modules with different frequencies in the same server, all the memory modules
run at the lowest frequency.
• When a 4 GB or more of memory (physical or logical) is installed, part of the 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 server configuration, and the
configured PCI options.
Optical drive:
• UltraSlim DVD-ROM combo
• Multi-burner
Hard disk drive expansion bays (depending on the model):
• Four 2.5-inch hot-swap SAS/SATA hard disk drive bays
• Four 2.5-inch simple-swap SAS/SATA hard disk drive bays
• Eight 2.5-inch hot-swap SAS/SATA hard disk drive bays
Chapter 2. About the Lenovo System x3250 M6 server 5

• Eight 2.5-inch simple-swap SAS/SATA hard disk drive bays
• Four 3.5-inch hot-swap SAS/SATA hard disk drive bays
• Four 3.5-inch simple-swap SATA hard disk drive bays
Attention: As a general consideration, do not mix standard 512 byte and advanced 4 KB format drives
in the same Redundant Array of Independent Disks (RAID) array because doing so might lead to
potential performance issues.
Peripheral Component Interconnect (PCI) Express expansion slots:
The server supports two PCIe riser slots on the riser card:
• Slot 1: dedicated to the ServeRAID M1210 SAS/SATA controller
• Slot 2: supports one PCI Express Gen3 x8 half-length, full-height adapter
Power supply (depending on the model):
• One fixed 300-watt power supply
• One or two 460-watt power supplies (hot-swap when two installed)
RAID controller:
ServeRAID C110 capabilities that support RAID levels 0, 1, 5, and 10

Integrated functions:
• Integrated Management Module 2.1 (IMM2.1), which consolidates multiple management functions in
a single chip
• Intel i350-AM2 Gigabit Ethernet controller and Wake on LAN support
• Universal Serial Bus (USB):
– Two USB 3.0 connectors on the front
Note: Due to the limitation of USB 3.0 connectors, the front USB connectors are not usable for the
VMware ESXi 5.5 hypervisor.
– Two USB 3.0 connectors on the rear
– One USB 3.0 internal connector on the system board for the USB hypervisor key
• Four-port integrated SATA controller
• One-port integrated SATA port for the optical drive (optional)
• One serial port header (functional with Serial Port Upgrade Kit installed)
• One video graphics array (VGA) connector on the rear
Video controller (integrated into IMM2.1):
• Matrox G200eR2
• SVGA compatible video controller
• AAVICA hardware video compression
• Video memory not expandable
• Maximum video resolution: 1600 x 1200 at 75 Hz
Size:
• 1U
• Height: 43 mm (1.69 inches)
• Depth: 576 mm (22.68 inches)

• Width:
– Without Electronic Industries Association (EIA) brackets: 434.6 mm (17.11 inches)
– With EIA brackets: 482 mm (18.98 inches)
• Maximum weight: 13.8 kg (30.36 lb)
Acoustical noise emissions:
Sound power: 5.4 bels for both idle and operating environment
In the idle environment, the server is only running the operating system. In the operating environment,
the microprocessor is active and the TDP is occupied 50%.
The noise emission level stated is the declared upper limit sound power level, in bels, for a random
sample of machines. All measurements are made in accordance with ISO 7779 and reported in
conformance with ISO 9296.
Environment:
• Air temperature:
– Server on:
– Server models with a lower-than-55 W CPU:
5°C to 40°C (41.0°F to 104.0°F); altitude: 0 m to 950 m (0 ft to 3117 ft)
The maximum system temperature decreases by 1°C (1.8°F) with every 175 m (574 ft) increase
in altitude above 950 m.
– Server models with a higher-than-55 W CPU:
10°C to 35°C (50.0°F to 95.0°F); altitude: 0 m to 950 m (0 ft to 3117 ft)
The maximum system temperature decreases by 1°C (1.8°F) with every 175 m (574 ft) increase
in altitude above 950 m.
– Server off: 5°C to 43°C (41°F to 109.4°F)
– Shipping: -40°C to 60°C (-40°F to 140°F)
• Maximum altitude: 3050 m (10000 ft)
• Humidity:
– Server on: 8% to 85%; maximum dew point: 24°C (75.2°F); maximum rate of change: 5°C (9°F)/
hour
– Server off: 8% to 85%; maximum dew point: 27°C (80.6°F)
• Particulate contamination:
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” on page 595.
When the operating temperature enhancement kit is installed, the temperature response for the fan
speed control is more accurate.
Heat output:
• Minimum configuration: 143 BTU per hour (42 watts)
• Maximum configuration: 710 BTU per hour (208 watts)
Electrical input:
• Sine-wave input (50 Hz to 60 Hz) required
• Input voltage low range:

– Minimum: 100 V ac
– Maximum: 127 V ac
• Input voltage high range:
– Minimum: 200 V ac
– Maximum: 240 V ac
• Input kilovolt-amperes (kVA):
– Minimum: 0.042 kVA
– Maximum: 0.508 kVA
Note: Power consumption and heat output vary depending on the number and type of optional features
installed and the power-management optional features in use.
What your server offers

The server offers the following features and technologies:
• Dynamic System Analysis (DSA)
The server comes with the Dynamic System Analysis (DSA) Preboot diagnostic program stored in the
integrated USB memory on the server. DSA collects and analyzes system information to aid in diagnosing
server problems, as well as offering a rich set of diagnostic tests on the major components of the server.
DSA creates a DSA log, which is a chronologically ordered merge of the system-event log (as the IPMI
event log), the Integrated Management Module 2.1 (IMM2.1) event log (as the ASM event log), and the
operating-system event logs. You can send the DSA log as a file to Lenovo Support or view the
information as a text file or Hypertext Markup Language (HTML) file.
• Features on Demand
If the Features on Demand feature is integrated in the server or in an optional device that is installed in the
server, you can purchase an activation key to activate the feature. For information about Features on
Demand, go to https://fod.lenovo.com/lkms.
• ServerGuide Setup and Installation CD
You can download the ISO image of the CD from the Web site, provides programs to help you set up the
server and install a Windows operating system. The ServerGuide program detects installed optional
hardware devices and provides the correct configuration programs and device drivers. For more
information about the ServerGuide Setup and Installation CD, see “Using the ServerGuide Setup and
Installation CD” on page 27.
• Lenovo XClarity Administrator
Lenovo XClarity Administrator is a centralized resource-management solution that enables administrators
to deploy infrastructure faster and with less effort. The solution seamlessly integrates into System x,
ThinkServer, and NeXtScale servers, as well as the Flex System converged infrastructure platform.
Lenovo XClarity Administrator provides the following features:
– Intuitive graphical user interface
– Automated discovery and inventory
– Firmware updates and compliance
– Configuration patterns
– Bare metal deployment
– Security management
– Upward integration
– Representational state transfer (REST) application programming interfaces and Windows PowerShell

– Simple network management protocol (SNMP), system log, and e-mail forwarding
For more information, see “Using Lenovo XClarity Administrator ” on page 39.
• Lenovo XClarity Energy Manager
Lenovo XClarity Energy Manager is a tool for data center power management. It models the data center
physical hierarchy and monitors power and temperature at the server level and the group level. By
analyzing power and temperature data, Lenovo XClarity Energy Manager helps you improve business
continuity and increase power efficiency. For more information, go to:
https://datacentersupport.lenovo.com/us/en/solutions/lnvo-lxem
• Lenovo ThinkServer Power Planner
The Lenovo ThinkServer Power Planner program provides power consumption information and electric
current calculation based on the different configurations of servers and other devices. The program also
helps to plan servers and devices deployment in an efficient way.
For more information about using the Lenovo ThinkServer Power Planner program, refer to the help
system of the program.
• Lenovo XClarity Essentials OneCLI
Lenovo XClarity Essentials (LXCE) is a collection of server management utilities that provides a less
complicated method to enable customers to manage Lenovo ThinkSystem, System x, and Thinkserver
servers more efficiently and cost-effectively.
– Lenovo XClarity Essentials Bootable Media Creator (BoMC) is a software application that can be used to
create bootable media. The bootable media can be used to apply firmware updates, run preboot
diagnostics, and deploy Microsoft Windows operating systems on the supported ThinkSystem, System
x, and BladeCenter systems.
– Lenovo XClarity Essentials OneCLI is a collection of several command line applications, which can be
used to configure the server, collect service data for the server, update firmware and device drivers,
and perform power-management functions on the server.
– XClarity Essentials UpdateXpress is a software application which can be used to acquire and apply
UpdateXpress System Packs (UXSP) and individual updates to your local or remote system. For more
information, go to https://support.lenovo.com/us/en/documents/LNVO-CENTER.
• Integrated Management Module 2.1 (IMM2.1)
The Integrated Management Module 2.1 (IMM2.1) combines service processor functions, video controller,
and remote presence and blue-screen capture features in a single chip. The IMM2.1 provides advanced
service-processor control, monitoring, and alerting function. If an environmental condition exceeds a
threshold or if a system component fails, the IMM2.1 lights LEDs to help you diagnose the problem,
records the error in the IMM2.1 event log, and alerts you to the problem. Optionally, the IMM2.1 also
provides a virtual presence capability for remote server management. The IMM2.1 provides remote server
management through the following industry-standard interfaces:
– Intelligent Platform Management Interface (IPMI) 2.0
– Simple Network Management Protocol (SNMP) 3.0
– Common Information Model (CIM)
– Web browser
For more information, see “Using the Integrated Management Module 2.1 (IMM2.1)” on page 35 and the
Integrated Management Module II User’s Guide at:
http://www.lenovo.com/support
• Integrated network support
The server comes with an integrated dual-port Intel Gigabit Ethernet controller, which supports
connection to a 10 Mbps, 100 Mbps, or 1000 Mbps network. For more information, see “Ethernet
controller information” on page 38.

• Integrated Trusted Platform Module (TPM)
This integrated security chip performs cryptographic functions and stores private and public secure keys.
It provides the hardware support for the Trusted Computing Group (TCG) specification. You can
download the software to support the TCG specification.
Trusted Platform Module (TPM) has two versions - TPM 1.2 and TPM 2.0. The server has TPM 1.2 device
installed by default. Some servers could be updated to TPM 2.0. You can change the TPM version from
1.2 to 2.0 and back again. TPM configurations can be accessible through the System Settings ➙
Security menu of the Setup Utility program. For more information, see ““Using the Setup Utility program””
on page 29.
• Large data-storage capacity and hot-swap capability
The server supports a maximum of eight 2.5-inch hot-swap or simple-swap Serial Attached SCSI (SAS) or
Serial ATA (SATA) hard disk drives, or four 3.5-inch hot-swap or simple-swap SAS/SATA hard disk drives,
depending on the server model.
• Large system-memory capacity
The server supports up to 64 GB of system memory. The memory controller supports error correcting
code (ECC) for up to four industry-standard PC4-17000 (DDR4-2133) UDIMMs.
• Mobile access to the Lenovo Service Information Web site
The server provides a QR code on the system service label, which is on the cover of the server. You can
scan the QR code using a QR code reader and scanner with a mobile device to get quick access to the
Lenovo Service Information Web site. The Lenovo Service Information Web site provides additional
information for server support, such as parts installation and replacement videos, and error codes for
server support.
The following illustration shows the QR code
http://support.lenovo.com/us/en/products/servers/lenovo-x86-servers/ lenovo-system-x3250-m6
Figure 3. QR code
• Multi-core processing
The server supports an Intel Pentium, Celeron, Core i3, or Xeon E3-1200 v5 series multi-core
microprocessor.
• PCIe adapter capabilities
The server has two PCIe interface slots. Both slots can support PCI Express adapters. See “Installing an
adapter” on page 114 for detailed information.
• Cooling and optional power capabilities
The server supports four speed-controlled simple-swap fans for a full configuration. The server comes
with one 300-watt fixed power supply, or one 460-watt hot-swap power supply installed. The server
supports a maximum of two 460-watt hot-swap power supplies. For redundancy support on hot-swap
models, two power-supplies must be installed in the server. Two power supplies enable continued
operation if one of the power supplies fails.
• ServeRAID support
The standard RAID adapter provides RAID levels 0, 1, and 10. Additional optional RAID adapters that
provide RAID level 5 are available for purchase. The ServeRAID M5200 Series adapters provide RAID level
6 if a Features on Demand upgrade key for RAID is available.

• System-management capabilities
The server comes with an Integrated Management Module 2.1 (IMM2.1). The IMM2.1, when used with the
system-management software that comes with the server, enables you to manage the functions of the
server locally and remotely. The IMM2.1 also provides system monitor, event record, and network alert
capability. The system-management connector for the IMM2.1 is on the rear of the server.
• UEFI-compliant server firmware
The Unified Extensible Firmware Interface (UEFI) firmware offers several features, including UEFI version
2.1 compliance; enhanced reliability, availability, and serviceability (RAS), and basic input/output system
(BIOS) compatibility support. UEFI replaces the traditional BIOS interface with a better 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 Disk Operating System (DOS).
• VMware ESXi embedded hypervisor
An optional USB flash device with VMware ESXi embedded hypervisor software is available for purchase.
Hypervisor is virtualization software that enables multiple operating systems to run on a host system at the
same time. For more information, see “Using the embedded hypervisor” on page 38.
Reliability, Availability, and Serviceability

Three important computer design features are reliability, availability, and serviceability (RAS). The RAS
features help to ensure the integrity of the data that is stored on the server, the availability of the server when
you need it, and the ease with which you can diagnose and correct problems.
Your server has the following RAS features:

• 3-year parts and 3-year labor limited warranty (Machine Type 3633)
• 1-year parts and 1-year labor limited warranty (Machine Type 3943)
• Backup BIOS switching under the control of the Integrated Management Module 2.1 (IMM2.1)
• 24-hour support center
• Call Home Service
• First Failure Data Capture (FFDC) for determining failure root cause
• Extended Error Handling (EEH) for PCIe host and root complex, PCIe link, and PCIe adapter failures
• Power-supply error detection
• VRD Fault Detection
• I/O Fault Handling
• Microprocessor Internal Error Detection
• Microprocessor Internal Thermal Trip
• Error correcting code (ECC) L2 cache and system memory
• Redundant hot-swap power supplies
• Hot-swap hard disk drives
• Advanced memory features:
– Single-bit memory error detection
– Single-bit memory error hardware correction
– Multi single-bit memory error detection
• Microprocessor Throttling
• Memory Thermal Throttling
• Predictive Failure Analysis (PFA) alerts
• Integrated management module (IMM)
• system-management monitoring through the Inter-Integrated Circuit (IC) protocol bus
• Standby voltage for system-management features and monitoring
• Power managed and Advanced Configuration and Power Interface (ACPI) compliant

• Power-on self-test (POST)
• System-error logging (POST and IMM)
• Error codes and messages
• Information and light path diagnostics LED panels
• Memory SPD and TruDDR4 Initiative
• NIC Failover Support
• Automatic restart on nonmaskable interrupt (NMI)
• Force O/S-dump (NMI Button)
• Boot from USB Device
• Remote System Reboot
• Automatic error retry and recovery
• Excessive Temperature Recovery
• Restore default CMOS settings button
• Vital product data (VPD) unique identifiers on blade server and all major electronic components with
information stored in nonvolatile memory for remote viewing
• Ambient Temperature monitors and alerts
• Memory Temperature monitors and alerts
• Processor Temperature monitors and alerts
• Upgradeable POST, UEFI, diagnostics, IMM firmware, and read-only memory (ROM) resident code, locally
or over the LAN
• On-Board Pre-Boot Diagnostics
• Ethernet Diagnostics
• RAID Diagnostics
• Installation and Service Guide
Turning on or turning off the server

When the server is connected to an ac power source but is not turned on, the operating system does not run,
and all core logic except for the Integrated Management Module 2.1 (IMM2.1) is shut down.
However, the server can respond to requests from Integrated Management Module 2.1 (IMM2.1), such as a
remote request to turn on the server. The power-on LED flashes to indicate that the server is connected to ac
power but is not turned on.
Turning on the server

Approximately 20 seconds after the server is connected to ac power, one or more fans might start running to
provide cooling and the power-on button LED starts blinking quickly. Approximately one to three minutes
after the server is connected to ac power, the power-control button becomes active and the blink of the
power-on button LED turns slow.
You can turn on the server by pressing the power-control button.
You also can turn on the server through the Wake on LAN feature if supported by the operating system. You
can send a request through the Wake on LAN feature to turn on the server remotely.
Besides, if a power failure occurs while the server is turned on, the server will restart automatically when
power is restored.
Turning off the server

Use this information to turn off the server.
When you turn off the server and leave it connected to ac power, the server can respond to requests from the
Integrated Management Module 2.1 (IMM2.1), such as a remote request to turn on the server. While the

server remains connected to ac power, one or more fans might continue to run. To remove all power from the
server, you must disconnect the server from the power source.
Some operating systems require an orderly shutdown before you turn off the server. For information about
shutting down the operating system, see your operating-system documentation or help system.
CAUTION:
power source.
2
1
The server can be turned off in any of the following ways:

• 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 turns off automatically.
• 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.
• If the operating system stops functioning, you can press and hold the power-control button for more than
four seconds to turn off the server.
• The server can be turned off through Wake on LAN.
Note: When you install any PCIe adapter, the power cords must be disconnected from the power source
before you remove the PCI riser-card assembly. Otherwise, the Wake on LAN feature might not work.
• The Integrated Management Module 2.1 (IMM2.1) can turn off the server as an automatic response to a
critical system failure.

Chapter 3. Component locations
This chapter provides information to help you locate server components.
Note: The illustrations in this document might differ slightly from your server.
Front view
The following illustration shows the controls, LEDs, and connectors on the front of the server.
Note: * Available on server models with hot-swap hard disk drives
Figure 4. Front view of server models with four 3.5-inch hard disk drives
1 Rack release latch (left) 2 Operator information panel
3 USB connector 1 4 USB connector 2
5 Optical drive bay 6 Optical drive activity LED
7 Optical drive eject button 8 Rack release latch (right)
9 Hard disk drive status LED* (yellow) 10 Hard disk drive activity LED* (green)
11 Hard disk drive bay 3 12 Hard disk drive bay 2
Figure 5. Front view of server models with four 2.5-inch hard disk drives
9 Rack release latch (right) 10 Hard disk drive bay 7

13 Hard disk drive bay 1 14 Hard disk drive status LED* (yellow)
15 Hard disk drive activity LED* (green) 16 Optical drive eject button
17 Optical drive activity LED 18 Optical drive bay
Figure 6. Front view of server models with eight 2.5-inch hard disk drives
9 Rack release latch (right) 10 Hard disk drive bay 7
13 Hard disk drive bay 1 14 Hard disk drive status LED* (yellow)
15 Hard disk drive activity LED* (green) 16 Optical drive eject button
17Optical drive activity LED 18 Optical drive bay
• Rack release latches:

Press the latches on each front side of the server to remove the server from the rack.
• Hard disk drive activity LED:
This LED is used on hot-swap SAS or SATA hard disk drives. When this LED is flashing, it indicates that
the drive is in use.
• Hard disk drive status LED:
This LED is used on hot-swap SAS or SATA hard disk drives. When this LED is lit, it indicates that the drive
has failed. If an optional 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 this LED is flashing rapidly (three
flashes per second), it indicates that the controller is identifying the drive.
• USB connectors:
Connect a USB device, such as a USB mouse, keyboard, or other device to any of these connectors.
• Optical drive eject button:
Press this button to eject the disc tray from the optical drive.
• Optical drive activity LED:
When this LED is lit, it indicates that the optical drive is in use.
• Operator information panel:

This panel contains controls and LEDs that provide information about the status of the server.
Rear view
The following illustrations show the connectors and LEDs on the rear of the server.
Figure 7. Rear view of the server with fixed power-supply
1 Power-cord connector 2 Ethernet connector 2
3 PCI slot 1 4 PCI slot 2
5 NMI button 6 Ethernet connector 1 for system management
7 USB connectors 8 VGA connector
Figure 8. Rear view of the server with the redundant power-supply model
1 Power-cord connectors 2 Ethernet connector 2
3 PCI slot 1 4 PCI slot 2
5 NMI button 6 Ethernet connector 1 for system management
7 USB connectors 8 Video connector
9 ac power LED (green) 10 dc power LED (green)
11 Power-supply error LED (yellow)
1 Ethernet link LED
2 Ethernet activity LED
• 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 connector.
• Ethernet activity LEDs: When these LEDs are lit, they indicate that there is activity between the server
and the network.
Chapter 3. Component locations 17

• ac power LED
• dc power LED
These LEDs show the status of the power supply. During normal operation, both of them are lit in green.
For more power-supply status information, see “Power-supply LEDs” on page 54.
• Power-supply error LED: When this yellow LED is lit, it indicates that the power supply has failed.
• Power cord connector: Connect the power cord to this connector.
• VGA connector: Connect a monitor to this connector.
• USB connectors: Connect a USB device, such as a USB mouse, keyboard, or other device to any of
these connectors.
• 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.1 through a single network cable.
• NMI button: Press this button to force a nonmaskable interrupt (NMI) to the microprocessor. By this way,
you can blue screen the server and take a memory dump. You might have to use a pen or the end of a
straightened paper clip to press the button.
Note: Use this button only when directed by the Lenovo service support.
• PCI slot 1: This slot is dedicated to ServeRAID M1210 SAS/SATA controller.
• PCI slot 2: This slot supports one PCI Express Gen3 x8 half-length, full-height adapter.
Operator information panel

The following illustration shows the controls and LEDs on the operator information panel.
Figure 9. Operator information panel
1 Power-control button and power- Press this button to turn on or turn off the server manually. The states of the
on LED power-on LED are as follows:
• Off:
Power is not present, otherwise the power supply or the LED itself has
failed.
• Flashing rapidly (four times per second):
The server is turned off and is not ready to be turned on. The power-control
button is disabled. This will last approximately 20 seconds.
• Flashing slowly (once per second):
The server is turned off and is ready to be turned on. You can press the
power-control button to turn on the server.
• On: The server is turned on.
2 Reset button Press this button to reset the server and run the power-on self-test (POST).
You might have to use a pen or the end of a straightened paper clip to press
the button.
3 Hard disk drive activity LED When this LED is flashing, it indicates that the associated hard disk drive is in
use.
4 System-locator LED Use this blue LED to locate the server among other servers visually. This LED
is also used as a presence detection button. You can use Lenovo XClarity
Administrator to light this LED remotely.

5 Check log LED When this yellow LED is lit, it indicates that a system error has occurred.
Check the event log for additional information. For more information, see
“Event logs” on page 56.
6 System-error LED When this yellow LED is lit, it indicates that a system error has occurred. For
more information, see “Event logs” on page 56.
7 USB connector 1 Connect a USB device, such as a USB mouse, keyboard, or other device to
8 USB connector 2 any of these connectors.
Server components
The following illustration shows the major components in the server.
The illustrations in this document might differ slightly from your hardware.
Figure 10. Server components

1 Server cover 4 2 Air baffle 4
3 Heat sink 2 4 Memory module 1
5 Fixed power supply* 2 6 Hot-swap power supply* 1
7 Chassis of 3.5-inch hard disk drive model with hot-swap 8 Power distribution board cover* 4
power supply* 4
9 Power distribution board* 2 10 2.5-inch simple-swap hard-disk-drive backplate

assembly* 2
11 3.5-inch simple-swap hard-disk-drive backplate 12 2.5-inch hot-swap hard-disk-drive backplane* 1

assembly* 2
13 3.5-inch hot-swap hard-disk-drive backplane* 1 14 Security bezel 3
15 Chassis of 2.5-inch hard disk drive model with fixed 16 Optical drive 1
power supply* 4
17 3.5-inch hard disk drive filler* 4 18 3.5-inch hot-swap hard disk drive* 1
19 3.5-inch simple-swap hard disk drive* 1 20 2.5-inch hot-swap hard disk drive* 1
21 2.5-inch simple-swap hard disk drive* 1 22 2.5-inch hard disk drive filler (for two hard disk drives)*
3
23 2.5-inch hard disk drive filler (for one hard disk drive)* 1 24 Front I/O assembly 1
25 System board 2 26 RAID adapter battery or flash power module holder* 4
27 System fan 1 28 Microprocessor 2
29 PCI riser-card assembly* 1 30 RAID card* 1
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. This 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.
Notes:
• * Available on some models
• 1 Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your responsibility. If Lenovo
installs a Tier 1 CRU at your request, you will be charged for the installation.
• 2 Tier 2 customer replaceable unit (CRU): You may install a Tier 2 CRU yourself or request Lenovo to install
it, at no additional charge, under the type of warranty service that is designated for your server.
• 3Structural parts: Purchase and replacement of structural parts (such as chassis assembly, cover, and
bezel) is your responsibility. If Lenovo acquires or installs a structural part at your request, you will be
charged for the service.
• 4Consumable parts: Parts that are purchased separately and not covered by the Lenovo Statement of
Limited Warranty.
Before servicing a Lenovo product, ensure that you read and understand “Safety” on page v. Use only parts
provided by Lenovo for replacement. For a complete listing of FRU information, such as FRU part numbers
and supported server models, go to:
http://www.lenovo.com/serviceparts-lookup

System-board connectors
The following illustration shows the connectors on the system board.
Figure 11. Connectors on the system board
1 PCI riser card connector 2 Microprocessor power connector
3 Power supply connector 4 Backplane power connector
5 DIMM slot 1 6 DIMM slot 2
7 DIMM slot 3 8 DIMM slot 4
9 Power distribution board connector 10 System fan 1 connector
11 System fan 2 connector 12 System fan 3 connector
13 System fan 4 connector 14 Mini-SAS connector
15 SATA optical drive connector 16 Operation information panel connector
17 Coin-cell battery connector 18 Front USB connector
19 USB hypervisor key connector 20 Operating temperature enhancement kit connector
System-board switches and jumpers

This topic helps you locate the jumpers and switches on the system board and get familiar with their
functions.
Important:
• Before you change any switch settings or move any jumpers, turn off the server. Then, disconnect all
power cords and external cables. Review the information in “Safety” on page v, “Before removing or
installing server components” on page 93, and “Turning off the server” on page 12.

• Any system-board switch or jumper block that is not shown in the illustrations in this document are
reserved.
• If there is a clear protective sticker on the switch blocks, you must remove and discard it to access the
switches.
87 654 321
5
On
Off
1 2 3
1 2 3
3
2
1
1
2
3
Figure 12. Switches and jumpers on the system board
1 Clear CMOS jumper 2 UEFI boot backup jumper (JP24)
3 TPM physical presence jumper (JP39) 4 Share NIC jumper
5 SW1 switch block
The following table describes the jumpers on the system board.
Table 2. Jumpers definition
Jumper name Description
Clear CMOS jumper

• Pins 1 and 2 (default): Keep the CMOS data.
• Pins 2 and 3: Clear the CMOS data.
UEFI boot backup
• Pins 1 and 2 (default): Load the primary server firmware ROM page.
jumper
• Pins 2 and 3: Boot from backup and load the secondary (backup) server firmware ROM
page.

Table 2. Jumpers definition (continued)
Jumper name Description
TPM physical presence

• Pins 1 and 2: Default off
jumper
• Pins 2 and 3: Indicates a physical presence to the system TPM.
Share NIC jumper

• Pins 1 and 2: Default on. Share LAN.
• Pins 2 and 3: Set Ethernet connector 1 as the dedicated management port of IMM.
If no jumper is present, the server responds as if the pins are set to the default.
Note: Changing the position of the UEFI boot backup 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.
Table 3. SW1 switch block definition
Switch number Default position Description

1, 3, 4, 5, 6, 7, 8 Off Reserved.
2 Off Power-on password overrides. Changing the position of this switch
bypasses the power-on password check the next time the server is
turned on and starts the Setup Utility so that you can change or
delete the power-on password. You do not have to move the switch
back to the default position after the power-on password in
overridden.
Changing the position of this switch does not affect the
administrator password check if an administrator password is set.
See “Passwords” on page 33 for additional information about

passwords.
System-board LEDs
The following illustration shows the light-emitting diodes (LEDs) on the system board.

Figure 13. LEDs on the system board
1 Complex Programmable Logic Device (CPLD) heartbeat 2 Power LED

LED
3 IMM heartbeat LED 4 System-error LED
5 System-locator LED 6 Field-Programmable Gate Array (FPGA) error LED

Chapter 4. Configuration information
This chapter provides information about updating the firmware and using the configuration utilities.
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.
• Before you update the firmware, be sure to back up any data that is stored in the Trusted Platform Module
(TPM), in case any of the TPM characteristics are changed by the new firmware. For instructions, see your
encryption software documentation.
• 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.
Lenovo XClarity Essentials OneCLI is a collection of command line applications that can be used to
manage Lenovo servers. Its update application can be used to update firmware and device drivers for
your servers. The update can be performed within the host operating system of the server (in-band) or
remotely through the BMC of the server (out-of-band). Specific details about updating firmware using
Lenovo XClarity Essentials OneCLI is available at: http://sysmgt.lenovofiles.com/help/topic/toolsctr_cli_
lenovo/onecli_c_update.html
• Lenovo XClarity Essentials UpdateXpress
Lenovo XClarity Essentials UpdateXpress provides most of OneCLI update functions through a graphical
user interface (GUI). It can be used to acquire and deploy UpdateXpress System Pack (UXSP) update
packages and individual updates. UpdateXpress System Packs contain firmware and device driver
updates for Microsoft Windows and for Linux. You can obtain Lenovo XClarity Essentials UpdateXpress
from the following location: https://support.lenovo.com/uu/en/solutions/lnvo-xpress.
• Lenovo XClarity Essentials Bootable Media Creator
You can use Lenovo XClarity Essentials Bootable Media Creator to create bootable media that is suitable
for applying firmware updates, running preboot diagnostics, and deploying Microsoft Windows operating
systems. You can obtain Lenovo XClarity Essentials BoMC from the following location: https://
datacentersupport.lenovo.com/uu/en/solutions/lnvo-bomc.
The firmware for the server is periodically updated and is available for download on the Lenovo Web site. To
check for the latest level of firmware, such as the UEFI firmware, device drivers, and Integrated Management
Module 2.1 (IMM2.1) firmware, go to
https://datacentersupport.lenovo.com.
Download the latest firmware for the server; then, install the firmware, using the instructions that are included
with the downloaded files.
When you replace a device in the server, you might have to update the firmware that is stored in memory on
the device or restore the pre-existing firmware from a CD or DVD image.
The following list indicates where the firmware is stored:

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

To configure your server, consider the following various aspects:
• Setup Utility
Setup Utility is part of the UEFI firmware. Use Setup Utility to change the startup-device sequence, set
system date and time, set passwords, and perform other configuration tasks. For more information, see
“Using the Setup Utility program” on page 29.
• Boot Manager
Boot Manager is part of the UEFI firmware. Use Boot Manager to override the startup sequence that is set
in the Setup Utility and temporarily assign a first startup device. For more information, see “Using the Boot
Manager program” on page 34.
• Lenovo ServerGuide Setup and Installation CD
The ServerGuide program is available on the ServerGuide Setup and Installation CD. This program
provides software-setup tools and installation tools that are designed for the server. Use this CD during
the installation of the server to configure basic hardware features, such as an integrated SAS/SATA
controller with RAID capabilities, and to simplify the installation of your operating system. For more
information, see “Using the ServerGuide Setup and Installation CD” on page 27.
Use the Integrated Management Module 2.1 (IMM2.1) to configure the server, update the firmware, update
the sensor data record/field replaceable unit (SDR/FRU) data, and remotely manage a network. For
information about using the IMM2.1, see “Using the Integrated Management Module 2.1 (IMM2.1)” on
page 35.
• VMware ESXi embedded hypervisor
An optional USB flash device with VMware ESXi embedded hypervisor software is available for purchase.
Hypervisor is virtualization software that enables multiple operating systems to run on a host system at the
same time. For more information about using the embedded hypervisor, see “Using the embedded
hypervisor” on page 38.
• Remote presence capability and blue-screen capture
The remote presence and blue-screen capture are integrated features of the Integrated Management
Module 2.1 (IMM2.1). The remote presence feature provides the following functions:
– Remotely viewing videos with graphics resolutions up to 1600 x 1200 at 75 Hz, regardless of the
system state
– Remotely accessing the server, using the keyboard and mouse from a remote client
– Mapping the CD or DVD drive, and USB flash drive on a remote client, and mapping ISO image files as
virtual drives that are available for use by the server
– Uploading a diskette image to the IMM2.1 memory and mapping it to the server as a virtual drive
The blue-screen capture feature captures the video display contents before the IMM2.1 restarts the server
when the IMM2.1 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 36.

• Ethernet controller configuration
For information about configuring the Ethernet controller, see “Ethernet controller information” on page
38.
• Features on Demand
The server provides the Features on Demand (FoD) software Ethernet support. You can purchase a FoD
software upgrade key for Fibre Channel over Ethernet (FCoE) and iSCSI storage protocols. For more
information, see “Enabling Features on Demand Ethernet and Demand RAID software” on page 38.
You can use the config application and commands to view the current system configuration settings and
make changes to Lenovo XClarity Controller and UEFI. The saved configuration information can be used
to replicate or restore other systems. For information about configuring the server using Lenovo XClarity
Essentials OneCLI, see: http://sysmgt.lenovofiles.com/help/topic/toolsctr_cli_lenovo/onecli_c_settings_info_
commands.html.
• RAID configuration
For information about configuring RAID, see “Accessing RAID configuration utility” on page 39.
The following table lists the applications that are available for configuring and managing RAID.
Table 4. Server configuration and applications for configuring and managing RAID
RAID configuration (before RAID management (after installing

Server configuration operating system is installed) the operating system)
ServeRAID M1210 SAS/SATA

– LSI Utility: (Press Ctrl+C in Setup – MegaRAID Storage Manager
Controller
Utility when under the legacy (MSM),
ServeRAID M1215 SAS/SATA
BIOS boot.) – StorCLI (Command Line) Utility
Controller
ServeRAID M5210 SAS/SATA – ServerGuide for Storage Management
Controller – Human Interface Infrastructure
ServeRAID M5225-2 GB SAS/SATA (HII)
Controller
Software RAID
– Intel Utility: (Press Ctrl+I in Setup – Graphical utility (Windows only)
Utility when under the legacy – Command Line: rstcli (Windows)
BIOS boot) and mdadm (Linux) Utility for
– ServerGuide Storage Management
– Human Interface Infrastructure
(HII)
For more information about Human Interface Infrastructure (HII) and StorCLI, go to:
http://public.dhe.ibm.com/systems/support/ system_x_pdf/ ibm_doc_mpt2sas_hiic-2011-09_user-guide.
pdf
For more information about MegaRAID, go to:
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5073015
Using the ServerGuide Setup and Installation CD

Use this information as an overview for using the ServerGuide Setup and Installation CD.
The ServerGuide Setup and Installation CD provides software setup tools and installation tools that are
designed for your server. The ServerGuide program detects the server model and optional hardware devices
that are installed and uses that information during setup to configure the hardware. ServerGuide simplifies
the operating-system installations by providing updated device drivers and, in some cases, installing them
automatically.
Chapter 4. Configuration information 27

When using ServerGuide to deploy Windows 2008 series, ServerGuide might run into a blue screen on your
system with or without ServeRAID C110 enabled. To avoid this problem, do the following:
1. Set UEFI settings.
2. View the Device and I/O Ports setting.
3. Do one of the following and save the changes:
• If the ServeRAID C110 is enabled, change the onboard SATA ports as into RAID or IDE.
• If the ServeRAID C110 is not enabled, change the onboard SATA ports as into IDE.
After saving the settings, the system will return to normal when rebooting from ServerGuide.
You can download a free image of the ServerGuide Setup and Installation CD from: https://
support.lenovo.com/solutions/lnvo-toolkit
In addition to the ServerGuide Setup and Installation CD, you must have your operating-system disc to install
the operating system.
ServerGuide features
Available features might 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 read the online overview. Not
all features are supported on all server models.
The ServerGuide program has the following features:

• An easy-to-use interface
• Diskette-free setup, and configuration programs that are based on the detected hardware
• Device drivers that are provided for the server model and detected hardware
• Selectable operating-system partition size and file-system type during setup
• Online readme file with links to tips for your hardware and operating-system installation
• Setting ystem date and time
Setup and configuration overview

You can use the ServerGuide Setup and Installation CD to configure any supported Lenovo server model.
The setup program provides a list of tasks that are required to set up your server model. On a server with a
ServeRAID adapter or SAS/SATA controller with RAID capabilities, you can run the SAS/SATA RAID
configuration program to create logical drives.
Typical operating-system installation by using ServerGuide

This section details the ServerGuide typical operating-system installation.
The ServerGuide program can reduce the time for installing an operating system. It provides the device
drivers that are required for your hardware and for the operating system that you are installing. Refer to the
following list for a typical operating-system installation by using ServerGuide:
1. After you have completed the setup process, the operating-system installation program starts. (You
need your operating-system disc to complete the installation.)
2. The ServerGuide program stores information about the server model, service processor, hard disk drive
controllers, and Ethernet controllers. Then, the program checks the CD for any updated device drivers.
This information is stored and then passed to the operating-system installation program.
3. The ServerGuide program presents operating-system partition options that are based on your operating-
system selection and the installed hard disk drives.
4. The ServerGuide program prompts you to insert your operating-system CD and restart the server. At this
point, the installation program for the operating system takes control to complete the installation.

Operating-system installation without using ServerGuide
If you have already configured the server hardware and you are not using the ServerGuide program to install
your operating system, you can download operating-system installation instructions for the server from
https://datacentersupport.lenovo.com/us/en/solutions/server-os.
Using the Setup Utility program

Use the Unified Extensible Firmware Interface (UEFI) Setup Utility program to perform the following tasks:
• View configuration information.
• View and change assignments for devices and I/O ports.
• Set the date and time.
• Set and change passwords.
• Set the startup characteristics of the server and the order of startup devices.
• Set and change settings for advanced hardware features.
• View, set, and change settings for power-management features.
• View and clear error logs.
• Resolve configuration conflicts.
Starting the Setup Utility program

To start the Setup Utility program, do the following:
Step 1. Turn on the server.
Note: Approximately 5 seconds after the server is connected to power, the power-control button
becomes active.
Step 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.
Step 3. Select settings to view or change according to your needs.
Setup Utility menu choices

Use the Setup Utility main menu to view and configure the server settings.
The following choices are on the Setup Utility main menu for the UEFI. Depending on the version of the
firmware, some menu choices might differ slightly from these descriptions.
• System Information (available on the full Setup Utility menu only)

Select this choice to view information about the server. When you make changes through other choices in
Setup Utility, some of those changes are reflected in the system information; you cannot change settings
directly in the system information.
– System Summary
Select this choice to view configuration information, including the ID, speed, and cache size of the
microprocessors; machine type and model of the server; the serial number; the system UUID; and the
amount of installed memory. When you make configuration changes through other options in Setup
Utility, the changes are reflected in the system summary; you cannot change settings directly in the
system summary.
– Product Data (available on the full Setup Utility menu only)

Select this choice to view the system-board identifier, the revision level or issue date of the firmware,
the Integrated Management Module 2.1 (IMM2.1) and diagnostics code, and the version and date.
• 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 and remote console redirection. You also can 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).
– 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 the 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
setting 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 setting is Enable.
– Infinite Boot Retry
Select this choice to enable or disable UEFI to retry the legacy boot order infinitely. The default
setting is Disable.
– Non-Planar PXE
Select this choice to enable or disable non-system-board Preboot Execution Environment (PXE) for
legacy mode.
– BBS Boot
Select this choice to enable or disable legacy boot in BIOS Boot Specification (BBS) manner. The
default is Enable.
– Security
Select this choice to view or configure the Trusted Platform Module (TPM) support.
– Integrated Management Module 2.1 (IMM2.1)
Select this choice to view or change the settings for the Integrated Management Module 2.1 (IMM2.1).

– Power Restore Policy
Select this choice to set the mode of operation after power loss.
– Commands on USB Interface
Select this choice to enable or disable the Ethernet over USB interface on IMM2.1. The default
setting is Enable.
– Network Configuration
Select this choice to view the system management network interface port, the IMM2.1 MAC
address, the current IMM2.1 IP address, and host name; define the static IMM2.1 IP address, subnet
mask, and gateway address; specify whether to use the static IP address or have DHCP assign the
IMM2.1 IP address; save the network changes; and reset the IMM2.1.
– Reset IMM2.1 to Defaults
Select this choice to view or reset the IMM2.1 to the default settings.
– Reset IMM2.1
Select this choice to reset the IMM2.1.
– Recovery and RAS
Select this choice to view or change the POST attempts and system recovery settings.
– Backup Bank Management
Select this choice to view or change the backup bank management setting.
– Disk GPT Recovery
Select this choice to view or change the Disk GPT recovery options.
– POST Attempts
Select this choice to view or change the number of attempts to POST.
• POST Attempts Limit
Select this choice to view or change the Nx boot failure parameters.
– System Recovery
Select this choice to view or change system recovery settings.
• POST Watchdog Timer
Select this choice to view or enable the POST watchdog timer.
• POST Watchdog Timer Value
Select this choice to view or set the POST loader watchdog timer value.
• Reboot System on NMI
Select this choice to enable or disable restarting the system whenever a nonmaskable interrupt
(NMI) occurs. The default setting is Enable.
– Storage
Select this choice to view or change the storage device settings.
– Network
Select this choice to view or change the network device options, such as iSCSI.
– Drive Health
Select this choice to view the status of the controllers installed in the blade server.
• Date and Time (available on the full Setup Utility menu only)
Select this choice to set the date and time in the server, in 24-hour format (hour:minute:second).
• Start Options (available on the full Setup Utility menu only)

Select this choice to view or change the start options, including the startup sequence, PXE boot option,
and PCI device boot priority. Changes in the startup options take effect when you start the server.
The startup sequence specifies the order in which the server checks devices to find a boot record. The
server starts from the first boot record that it finds. If the server has Wake on LAN hardware and software
and the operating system supports Wake on LAN functions, you can specify a startup sequence for the
Wake on LAN functions. For example, you can define a startup sequence that checks for a disc in the CD-
RW/DVD drive, then checks the hard disk drive, and then checks a Ethernet controller.
• Boot Manager
Select this choice to view, add, delete, or change the device boot priority, boot from a file, select a one-
time boot, change the boot mode, or restart the system.
• System Event Log (available on the full Setup Utility menu only)
Select this choice to enter the System Event Manager, where you can view the POST event log and the
system-event log. You can use the arrow keys to move between pages in the error log.
POST event log contains the most recent error codes and messages that were generated during the
POST.
System-event log contains POST and system management interrupt (SMI) events and all events that are
generated by the baseboard management controller that is embedded in the Integrated Management
Module 2.1 (IMM2.1).
Important: If the system-error LED on the front of the server is lit but there are no other error indications,
clear the system-event log. Also, after you complete a repair or correct an error, clear the system-event
log to turn off the system-error LED on the front of the server.
– POST Event Viewer
Select this choice to enter the POST event viewer to view the POST error messages.
– System Event Log
Select this choice to view the system event log.
– Clear System Event Log
Select this choice to clear the system event log.
• User Security
Select this choice to set, change, or clear passwords. For more information, see “Passwords” on page 33.
– Set Power-on Password
Select this choice to set or change a power-on password. For more information, see “Power-on
password” on page 33.
– Clear Power-on Password
Select this choice to clear a power-on password. For more information, see “Power-on password” on
page 33.
– Set Administrator Password
Select this choice to set or change an administrator password. An administrator password is intended
to be used by a system administrator; it limits access to the full Setup Utility menu. If an administrator
password is set, the full Setup Utility menu is available only if you type the administrator password at
the password prompt. For more information, see “Administrator password” on page 34.
– Clear Administrator Password
Select this choice to clear an administrator password. For more information, see “Administrator
password” on page 34.
• Save Settings
Select this choice to save the changes that you have made in Setup Utility.

• Restore Settings
Select this choice to cancel the changes that you have made in Setup Utility and restore the previous
settings.
• Load Default Settings
Select this choice to cancel the changes that you have made in Setup Utility and restore the factory
settings.
• Exit Setup
Select this choice to exit Setup Utility. If you have not saved the changes that you have made in Setup
Utility, you will be asked whether you want to save the changes or exit without saving them.
Passwords
From the User Security menu choice, you can set, change, and delete a power-on password and an
administrator password.
The User Security 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.
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:
• 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.
• Remove the battery from the server, wait 30 seconds, and then reinstall it.
• Change the position of the power-on password switch by enabling switch 2 of the system board switch
block (SW1) to bypass the password check (see “System-board switches and jumpers” on page 21 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. For the safety information, see “Safety” on page v. Do not

change settings or move jumpers on any system-board switch or jumper blocks that are not shown in this
document.
The default position for all switches on the 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-20 printable ASCII characters for the password.
Attention: If you set an administrator password and then forget it, there is no way to change, override, or
remove it. You must replace the system board.
Using the Boot Manager program

Boot Manager is a built-in, menu-driven configuration program that you can use to temporarily redefine the
first startup device without changing settings in Setup Utility.
To use the Boot Manager program, do the following:
Step 1. Turn off the server.

Step 2. Restart the server.
Step 3. When the prompt <F12> Select Boot Device is displayed, press F12.
Step 4. Use the Up arrow and Down arrow keys to select an item from the menu and press Enter.
The next time the server starts, it returns to the startup sequence that is set in the Setup Utility.
Starting the backup server firmware

The system board contains a backup copy area for the server firmware. During the process of updating the
server firmware, if the primary copy of the server firmware becomes damaged, use this backup copy.
To force the server to start from the backup copy, turn off the server; then, place the UEFI boot backup
jumper in the backup position (pins 2 and 3) to enable the UEFI recovery mode. For the location of the UEFI
boot backup jumper, see “System-board switches and jumpers” on page 21.
Use the backup copy of the server firmware until the primary copy is restored. After the primary copy is
restored, turn off the server; then, move the UEFI boot backup jumper back to the primary position (pins 1
and 2).
Changing the Power Policy option to the default settings after loading
UEFI defaults
The default settings for the Power Policy option are set by the IMM2.1.
To change the Power Policy option to the default settings, do the following:
Note: Approximately 20 seconds after the server is connected to ac power, the power-control
button becomes active.

Step 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; otherwise if you do not
type the administrator password, a limited Setup Utility menu is available.
Step 3. Select System Settings ➙ Integrated Management Module, and then set Power Restore Policy
setting to Restore.
Step 4. Go back to System Configuration and Boot Management ➙ Save Settings.
Step 5. Go back and check the Power Policy setting to verify that it is set to Restore (the default).
Using the Integrated Management Module 2.1 (IMM2.1)

Integrated Management Module 2.1 (IMM2.1) is a second generation of the functions that were formerly
provided by the baseboard management controller hardware. It combines service processor functions, video
controller, and remote presence function in a single chip.
IMM2.1 supports the following basic system-management features:

• Alerts (in-band and out-of-band alerting, PET traps - IPMI style, SNMP, e-mail)
• Auto Boot Failure Recovery (ABR)
• Automatic Server Restart (ASR) when POST is not completed or the operating system hangs and the
operating system watchdog timer times out
• A virtual media key, which enables remote presence support (remote video, remote keyboard/mouse, and
remote storage)
• Boot sequence manipulation
• Command-line interface
• Configurations save and restore
• DIMM error assistance. The UEFI disables a failing DIMM that is detected during POST, and the IMM2.1
lights the associated system error LED
• Environmental monitor with fan speed control for temperature, voltages, fan failure, power supply failure,
and power backplane failure
• Intelligent Platform Management Interface (IPMI) Specification V2.0 and Intelligent Platform Management
Bus (IPMB) support
• Invalid system configuration (CONFIG) LED support
• Local firmware code flash update
• Nonmaskable interrupt (NMI) detection and reporting
• Operating-system failure blue screen capture
• PCI configuration data
• Power/reset control (power-on, hard and soft shutdown, hard and soft reset, schedule power control)
• Query power-supply input power
• ROM-based IMM2.1 firmware flash updates
• Serial over LAN (SOL)
• Serial port redirection over telnet or ssh protocols
• SMI handling
• System event log (SEL) - user readable event log
The IMM2.1 also provides the following remote server management capabilities through the ipmitool, a
management utility program:
• 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.
• 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.1, see the Integrated Management Module II User's Guide at:
http://publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.sysx.imm2.doc/ product_
page.html
Using the remote presence and blue-screen capture features

The remote presence and blue-screen capture features are integrated in the Integrated Management Module
2.1 (IMM2.1).
The remote presence feature provides the following functions:

• Remotely viewing video with graphics resolutions up to 1600 x 1200 at 75 Hz, regardless of the system
state
• Remotely accessing the server, using the keyboard and mouse from a remote client
• Mapping the CD or DVD drive, and USB flash drive on a remote client, and mapping ISO image files as
virtual drives that are available for use by the server
The blue-screen capture feature captures the video display contents before the IMM2.1 restarts the server
when the IMM2.1 detects an operating-system hang condition. A system administrator can use the blue-
screen capture to assist in determining the cause of the hang condition.
Obtaining the IMM2.1 host name

If you are logging on to the IMM2.1 for the first time after installation, the IMM2.1 defaults to DHCP. If a
DHCP server is not available, the IMM2.1 uses a static IP address of 192.168.70.125. The default IPv4 host
name is “IMM-” (plus the last 12 characters on the IMM2.1 MAC address). The default host name also comes
on the IMM2.1 network access tag, which is attached to the power supply on the rear of the server. You can
get the host name without starting the server.
The IPv6 link-local address (LLA) is derived from the IMM2.1 default host name. To derive the link-local
address, do the following:
Step 1. Take the last 12 characters on the IMM2.1 MAC address (for example, 5CF3FC5EAAD0).
Step 2. Separate the number into pairs of hexadecimal characters (for example, 5C:F3:FC:5E:AA:D0).
Step 3. Separate the first six and last six hexadecimal characters.
Step 4. Add “FF” and “FE” in the middle of the 12 characters (for example, 5C F3 FC FF FE 5E AA D0).
Step 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).
Step 6. Flip the seventh binary character from left (0 to 1 or 1 to 0), which results in 01011110 F3 FF FE 5E
AA D0.
Step 7. Convert the binary back to hexadecimal (for example, 5E F3FCFFFE5EAAD0).

Obtaining the IP address for the IMM2.1
To access the Web interface to use the remote presence feature, you need the IP address or host name of
the IMM2.1. You can obtain the IMM2.1 IP address through the Setup Utility and you can obtain the IMM2.1
host name from the IMM2.1 network access tag. The server comes with a default IP address
(192.168.70.125) for the IMM2.1.
To obtain the IP address, do the following:
becomes active.
Step 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.
Step 3. Select System Settings from the Setup Utility main menu.
Step 4. Select Integrated Management Module.
Step 5. Select Network Configuration.
Step 6. Find the IP address and write it down.
Step 7. Exit Setup Utility.
Logging in to the Web interface

To log in to the IMM2.1 Web interface, do the following:
Step 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 IMM2.1 to which you want to connect.
Note: If you are logging on to the IMM2.1 for the first time after installation, the IMM2.1 defaults to
DHCP. If a DHCP host is not available, the IMM2.1 assigns a static IP address of 192.168.70.125.
The IMM2.1 network access tag provides the default host name of the IMM2.1 and does not
require you to start the server.
Step 2. On the Login page, type the user name and password. If you are using the IMM2.1 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 IMM2.1 is set initially with a user name of USERID and password of PASSW0RD (with a
zero, not the letter O). You have read and write access. You must change the default password the
first time you log in.
Step 3. Click Log in to start the session. The System Status and Health page provides a quick view of the
system status.
Note: If you boot to the operating system while in the IMM2.1 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 Server® 2008 or 2012 console. This might also affect
blue-screen capture features.
netsh advfirewall firewall set icmpsetting type=8 mode=ENABLE
By default, the icmp packet is blocked by Windows Server firewall. The IMM2.1 GUI will then change to the
“OS booted” status after you change the setting as indicated above in both the Web and CLI interfaces.

Using the embedded hypervisor
The VMware ESXi embedded hypervisor is available on the optional Lenovo USB flash device.
The USB flash device can be connected to the USB connectors on the system board. To locate the
connectors, see “System-board connectors” on page 21. Hypervisor is a type of software that enables
multiple operating systems to run on a host system at the same time. The USB flash device is required to
activate the hypervisor.
To start using the embedded hypervisor, you must add the USB flash device to the startup sequence in the
Setup Utility.
To add the USB flash device to the startup sequence, do the following:
becomes active.
Step 2. When the prompt <F1> Setup is displayed, press F1.
Step 3. From the Setup Utility main menu, select Boot Manager.
Step 4. Select Add Boot Option; then, select Generic Boot Option ➙ Embedded Hypervisor. Press
Enter, and then press Esc.
Step 5. Select Change Boot Order ➙ Change the order. Use the up 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.
Step 6. Select Save Settings and then select Exit Setup.
If the embedded hypervisor flash device image becomes corrupt, you can download the image from http://
www-03.ibm.com/systems/x/os/vmware/esxi/.
For additional information and instructions, see VMware vSphere documentation at http://www.vmware.com/
support/pubs/.
Ethernet controller information

The Ethernet controllers are integrated on the system board. They provide an interface for connecting to a 10
Mbps, 100 Mbps, or 1 Gbps network and provide full-duplex (FDX) capability, which enables simultaneous
transmission and reception of data on the network. If the Ethernet connectors in the server support auto-
negotiation, the controllers detect the data-transfer rate (10BASE-T, 100BASE-TX, or 1000BASE-T) and
duplex mode (full-duplex or half-duplex) of the network and automatically operate at that rate and mode.
You do not have to set any jumpers or configure the controllers. However, you must install a device driver to
enable the operating system to address the controllers.
To find device drivers, go to http://www.lenovo.com/support.
Enabling Features on Demand Ethernet and Demand RAID software

You can activate the Features on Demand (FoD) software upgrade key for the following:
• Fibre Channel over Ethernet (FCoE)
• iSCSI storage protocol
• RAID

The FCoE and iSCSI storage protocols and RAID are integrated in the IMM2.1.
For more information, see the Lenovo Features on Demand User’s Guide. To download the document, go to
https://fod.lenovo.com/lkms, log in, and click Help.
Accessing RAID configuration utility

Through the Setup Utility, you can access utilities to configure RAID arrays.
The specific procedure for configuring arrays depends on the RAID card that you are using. For details, see
the documentation for your RAID card. To access the utility for your RAID card, do the following:
becomes active.
Step 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.
Step 3. Select System Settings ➙ Storage.
Step 4. Select the device driver for your RAID card and press Enter. Then, follow the instructions in the
documentation for your RAID card.
Lenovo XClarity Essentials OneCLI

Lenovo XClarity Essentials (LXCE) is a collection of server management utilities that provides a less
complicated method to enable customers to manage Lenovo ThinkSystem, System x, and Thinkserver
servers more efficiently and cost-effectively.
• Lenovo XClarity Essentials Bootable Media Creator (BoMC) is a software application that can be used to
create bootable media. The bootable media can be used to apply firmware updates, run preboot
diagnostics, and deploy Microsoft Windows operating systems on the supported ThinkSystem, System x,
and BladeCenter systems.
• Lenovo XClarity Essentials OneCLI is a collection of several command line applications, which can be used
to configure the server, collect service data for the server, update firmware and device drivers, and
perform power-management functions on the server.
• XClarity Essentials UpdateXpress is a software application which can be used to acquire and apply
UpdateXpress System Packs (UXSP) and individual updates to your local or remote system. For more
information, go to https://support.lenovo.com/us/en/documents/LNVO-CENTER.
Using Lenovo XClarity Administrator

The initial setup of Lenovo XClarity Administrator includes the following:
• Preparing the network
• Installing and configuring the Lenovo XClarity Administrator virtual appliance
• Managing systems
• Setting up automatic problem notification optionally
To manage systems based on the network topology that is implemented in your environment, there are a
number of different ways to connect manageable systems to the network and to set up the Lenovo XClarity
Administrator. If you plan to use Lenovo XClarity Administrator to manage the server, you must check for the
latest applicable Lenovo XClarity Administrator updates. For installing the Lenovo XClarity Administrator in

VMware ESXi-based and Hyper-V environments and downloading Lenovo XClarity Administrator updates, go
to:
https://support.lenovo.com/us/en/ documents/LNVO-XCLARIT
Lenovo XClarity Administrator offers a free, 90-day trial license that enables you to use all available features
(including operating-system deployment, firmware maintenance, and configuration management) for a
limited time. To continue using Lenovo XClarity Administrator after the 90–day trial period, you are required
to purchase a full-function-enablement license for each Lenovo XClarity Administrator instance. You can
purchase and download the license from:
https://support.lenovo.com/us/en/documents/lnvo-lxcaupd
Updating the Universal Unique Identifier (UUID)

The Universal Unique Identifier (UUID) must be updated when the system board is replaced. Use the Lenovo
XClarity Essentials OneCLI to update the UUID in the UEFI-based solution. Lenovo XClarity Essentials
OneCLI is an online tool that supports several operating systems; make sure that you download the version
for your operating system.
Notes: You can use Lenovo XClarity Provisioning Manager to update the UUID for the solution:
1. Start the solution and press F1 to display the Lenovo XClarity Provisioning Manager system setup
interface.
2. From the System Summary page, click Update VPD.
3. Update the UUID.
To download Lenovo XClarity Essentials OneCLI, go to the following site:
https://datacentersupport.lenovo.com/us/en/solutions/HT116433
Lenovo XClarity Essentials OneCLI sets the UUID in the Lenovo XClarity Controller. Select one of the
following methods to access the Lenovo XClarity Controller and set the UUID:
• Online from the target system, such as LAN or keyboard console style (KCS) access
• Remote access to the target system (LAN based)
Step 1. Copy and unpack the OneCLI package, which also includes other required files, to the solution.
Make sure that you unpack the OneCLI and the required files to the same directory.
Step 2. After you have OneCLI in place, use the following command syntax to set the UUID:
onecli config 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:
• Online authenticated LAN access, type the command:

Example that does not use the user ID and password default values:
onecli config set SYSTEM_PROD_DATA.SYsInfoUUID <uuid_value> --user <user_id>
--password <password>
Example that uses the user ID and password default values:
onecli config set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value>

• Online KCS access (unauthenticated and user restricted):
You do not need to specify a value for access_method when you use this access method.
Example:
Note: The KCS access method uses the IPMI/KCS interface, which requires that the IPMI
driver be installed.
• Remote LAN access, type the command:
Note: When using the remote LAN access method to access Lenovo XClarity Controller
using the LAN from a client, the host and the xcc_external_ip address are required
parameters.
[−−imm xcc_user_id:xcc_password@xcc_external_ip]
or
[−−bmc xcc_user_id:xcc_password@xcc_external_ip]
Where:
xcc_external_ip
The BMC/IMM/XCC external LAN IP address. There is no default value. This parameter
is required.
xcc_user_id
The BMC/IMM/XCC account name (1 of 12 accounts). The default value is USERID.
xcc_password
The BMC/IMM/XCC account password (1 of 12 accounts). The default value is
PASSW0RD (with a zero 0 not an O).
Note: BMC, IMM, or XCC external LAN IP address, account name, and password are all
valid for this command.
Example that does use the user ID and password default values:
Step 3. Restart the Lenovo XClarity Controller.
Step 4. Restart the solution.
Updating the DMI/SMBIOS data

The Desktop Management Interface (DMI) must be updated when the system board is replaced. Use the
Lenovo XClarity Essentials OneCLI to update the DMI in the UEFI-based solution. Lenovo XClarity Essentials
OneCLI is an online tool that supports several operating systems; make sure that you download the version
for your operating system.
Notes: You can use Lenovo XClarity Provisioning Manager to update the asset tag for the solution:
1. Start the solution and press F1 to display the Lenovo XClarity Provisioning Manager system setup
interface.
2. From the System Summary page, click Update VPD.
3. Update the asset tag information.
To download Lenovo XClarity Essentials OneCLI, go to the following site:
https://datacentersupport.lenovo.com/us/en/solutions/HT116433

Lenovo XClarity Essentials OneCLI sets the DMI in the Lenovo XClarity Controller. Select one of the following
methods to access the Lenovo XClarity Controller and set the DMI:
• Online from the target system, such as LAN or keyboard console style (KCS) access
• Remote access to the target system (LAN based)
Step 1. After you have Lenovo XClarity Essentials OneCLI in place, type the following commands to set the
DMI:
onecli config set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> [access_method]
onecli config set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> [access_method]
onecli config set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> [access_method]
Where:
<m/t_model>
The solution machine type and model number. Type mtm xxxxyyy, where xxxx is the machine
type and yyy is the solution model number.
<s/n>
The serial number on the solution. Type sn zzzzzzz, where zzzzzzz is the serial number.
<asset_method>
The solution 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:
• Online authenticated LAN access, type the command:

[−−imm xcc_user_id:xcc_password@xcc_internal_ip]
or
[−−bmc xcc_user_id:xcc_password@xcc_internal_ip]
Where:
xcc_internal_ip
The BMC/IMM/XCC internal LAN/USB IP address. The default value is 169.254.95.118.
xcc_user_id
The BMC/IMM/XCC account name (1 of 12 accounts). The default value is USERID.
xcc_password
Notes:
1. BMC, IMM, or XCC internal LAN/USB IP address, account name, and password are all
valid for this command.
2. If you do not specify any of these parameters, OneCLI will use the default values. When
the default values are used and OneCLI is unable to access the Lenovo XClarity
Controller using the online authenticated LAN access method, OneCLI will
automatically use the unauthenticated KCS access method.
Examples that do use the user ID and password default values:
onecli config set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model>
onecli config set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n>
onecli config set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>

• Online KCS access (unauthenticated and user restricted): You do not need to specify a
value for access_method when you use this access method.
Note: The KCS access method uses the IPMI/KCS interface, which requires that the IPMI
driver be installed.
The following commands are examples of not using the user ID and password default
values:
onecli config set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model>
onecli config set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n>
onecli config set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>
• Remote LAN access, type the command:
Note: When using the remote LAN access method to access Lenovo XClarity Controller
using the LAN from a client, the host and the xcc_external_ip address are required
parameters.
[−−imm xcc_user_id:xcc_password@xcc_external_ip]
or
[−−bmc xcc_user_id:xcc_password@xcc_external_ip]
Where:
xcc_external_ip
The BMC/IMM/XCC LAN IP address. There is no default value. This parameter is
required.
xcc_user_id
The BMC/IMM/XCC account (1 of 12 accounts). The default value is USERID.
xcc_password
Note: BMC, IMM, or XCC internal LAN/USB IP address, account name, and password are
all valid for this command.
Examples that do use the user ID and password default values:
onecli config set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> --host <xcc_ip>
onecli config set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> --host <xcc_ip>
onecli config set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> --host <xcc_ip>
Step 2. Restart the solution.
Configuring onboard SATA software RAID

You can configure onboard SATA software RAID by enabling the onboard SATA RAID functionality, creating
RAID volumes, deleting RAID volumes, and marking disks as spare.
Enabling the onboard SATA RAID functionality

Note: Use the arrow keys on the keyboard to make selections.
To enable onboard SATA RAID functionality, do the following:

1. Start the Setup Utility program. See “Starting the Setup Utility program” on page 29.
2. Select System settings ➙ Devices and I/O prots.
3. Select Onboard SATA mode and press Enter.
4. Select RAID and press Enter.

5. Press ESC twice to return to the main menu of the Setup Utility program.
6. Select Save Settings and press Enter.
7. Exit the Setup Utility program.
Creating RAID volumes

This section describes how to use the Intel Rapid Storage Technology enterprise UEFI HII to create RAID
volumes.
To create RAID volumes, do the following:

2. Select System settings ➙ Storage and press Enter.
3. Select Intel RSTe SATA Controller and press Enter.
4. Select Create RAID Volume and press Enter.
5. Type a proper RAID volume name in the Name field and press Enter.
6. Use the arrow keys to select a RAID level in the RAID Level field and press Enter.
7. Use the arrow keys to select a hard disk drive in the Select Disk field and press Enter.
8. If necessary, repeat step 7 to select multiple hard disk drives.
9. Use the arrow keys to select a stripe size in the Stripe Size field and press Enter.
10. Type a volume size in the Capacity (MB) field and press Enter.
11. Select Create Volume and press Enter.
12. When prompted, press Y to accept the warning message and create the volume.
13. If desired, return to step 4 to create additional RAID volumes.
Deleting RAID volumes

This section describes how to use the Intel Rapid Storage Technology enterprise UEFI HII to delete RAID
volumes.
To delete RAID volumes, do the following:

4. Use the arrow keys to select the RAID volume to be deleted in the RAID Volume field and press Enter.
5. Select Delete and press Enter.
6. When prompted, press Y to confirm the deletion of the selected RAID volume. Deleting a RAID volume
will reset the hard disk drives to non-RAID.
7. After deleting a RAID volume, you can:
• Return to step 4 to delete additional RAID volumes.
• See “Creating RAID volumes” on page 44 for RAID volume creation.
• Exit the Setup Utility program.
Marking disks as spare

To mark hard disk drives as spare drives, do the following:

4. Use the up and down arrow keys to select a Non-RAID physical disk in the Non-RAID Physical Disks
field and press Enter.
5. Select Mark as Spare and press Enter.
6. When prompted, press Y to confirm the operation.
Note: Marking a hard disk drive as a spare drive will remove all data on the drive.
Notes: If your server has one of the following Linux operating systems installed, continue with the
corresponding actions:
• For the Redhat Enterprise Linux 6.7 operating system, add the following line to the end of the /etc/mdadm.
conf file and restart the operating system.
POLICY domain=DOMAIN path=* metadata=imsm action=spare-same-slot
• For the SUSE Linux Enterprise Server 11.4 operating system, do the following:
1. Add the following line to the end of the /etc/mdadm.conf file.
POLICY domain=DOMAIN path=* metadata=imsm action=spare-same-slot
2. Run the following commands as a root user.
# chkconfig –s mdadmd on
# /etc/init.d/mdadmd start

Chapter 5. 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 589.
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 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 a Lenovo-approved warranty service provider, perform the following steps in the
order in which they are presented to diagnose a problem with your server.
Step 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 action might involve any of the following items:
• Hardware components
• Device drivers and firmware
• System software
• UEFI firmware
• System input power or network connections
Step 2. View the light path diagnostics LEDs, event logs, and error codes.
The following items are available to help you diagnose hardware and software problems easily:
• Light path diagnostics LEDs (see “Light path diagnostics” on page 53)
• Event logs (see “Event logs” on page 56)
• Software or operating-system error codes (see the documentation or tips on the
manufacturer's Web site)
Step 3. Run LXCE OneCLI and collect the system data.
Run LXCE OneCLI 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 on how to run OneCLI, see the LXCE OneCLI User Guide.
To download the latest version of OneCLI code and the LXCE OneCLI User Guide, go to https://
support.lenovo.com/us/en/documents/LNVO-DSA.
Step 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
https://datacentersupport.lenovo.com
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
Lenovo XClarity Essentials 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, go to:
For more information about the Bootable Media Creator program, go to:
https://support.lenovo.com/ us/en/documents/LNVO-BOMC
Be sure to separately install any listed critical updates that have a release date later than the
release date of the UpdateXpress System Pack or UpdateXpress image. Refer to the following
two steps for installing manual system updates.
b. Install manual system updates.
1. Determine the existing code levels.
In OneCLI Inventory Report, click Firmware/VPD to view system firmware levels, or click
Software to view operating-system levels.
2. Download and install updates for any code that is not at the latest level.
To display a list of available updates for the server, go to:
When you click an update, an information page is displayed, including a list of the
problems that the update fixes. Review this list for your specific problem; however, even if
your problem is not listed, installing the update might solve the problem.
Step 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.
To verify that the server supports the installed operating system, optional devices, and
software levels, go to http://www.lenovo.com/ serverproven/. If any hardware or software
component is not supported, remove the hardware or uninstall the software to determine
whether it is causing the problem. You must remove nonsupported hardware before you
contact IBM or an approved warranty service provider for support.

b. Make sure that the server, operating system, and software are installed and configured
correctly.
Many configuration problems are caused by loose power or signal cables or improperly seated
adapters. You might be able to solve the problem by turning off the server, reconnecting
cables, reseating adapters, and turning the server back on. For information about performing
the checkout procedure, see “Precautions before performing the checkout procedure” on
page 50. For information about configuring the server, see Chapter 4 “Configuration
information” on page 25.
Step 6. Consult the controller and management software documentation.
If the problem is associated with a specific function (for example, if a RAID hard disk drive is
marked offline in the RAID array), see the documentation for the associated controller and
management or controlling software to verify that the controller is correctly configured.
Problem determination information is available for many devices such as RAID and Ethernet
controllers.
For problems with operating systems or IBM software or devices, go to http://www.lenovo.com/

support.
Step 7. Check for troubleshooting procedures and retain tips.
Troubleshooting procedures and retain tips document known problems and suggested solutions.
To search for troubleshooting procedures and retain tips, go to http://www.lenovo.com/support.
Step 8. Use the troubleshooting tables.
To find a solution to a problem that has identifiable symptoms, see “Troubleshooting by symptom”
on page 61.
A single problem might cause multiple symptoms. Follow the troubleshooting procedure for the
most obvious symptom. If that procedure does not solve the problem, use the procedure for
another symptom, if possible.
If the problem remains, contact IBM or an approved warranty service provider for assistance with
additional problem determination and possible hardware replacement. To open an online service
request, go to http://www.ibm.com/support/ entry/portal/Open_service_request. Be prepared to
provide information about any error codes and collected data.
Opening an online service request

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 codes are 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.
Service bulletins
Lenovo continually updates the support Web site with the latest tips and techniques that you can use to
solve problem that you might have with the Lenovo System x3250 M6 server.
Chapter 5. Troubleshooting 49
To find service bulletins that are available for the Lenovo System x3250 M6 server, go to http://
www.lenovo.com/support and search for 3633 and 3943, and retain.
Checkout procedure
This section provides additional information for you to diagnose a problem.
Precautions before performing the checkout procedure

Before you perform the checkout procedure for diagnosing hardware problems, review the following
information.
• Read the safety information. See “Safety” on page v.

• Dynamic System Analysis (DSA) provides the primary methods of testing the major components of the
server, such as the system board, Ethernet controller, keyboard, mouse (pointing device), serial ports, and
hard disk drives. You can also use DSA to test some external devices. If you are not sure whether a
problem is caused by the hardware or by the software, you can use DSA to confirm that the hardware is
working properly.
• When you run DSA, a single problem might cause more than one error message. When this happens,
correct the cause of the first error message. The other error messages usually will not occur the next time
you run DSA.
Important: If multiple error codes or light path diagnostics LEDs indicate a microprocessor error, the
error might be related to the microprocessor or the microprocessor socket.
• Before you run DSA, you must determine whether the failing server is part of a shared hard disk drive
cluster (two or more servers sharing external storage devices). If it is part of a cluster, you can run all
diagnostic programs except the ones that test the storage unit (that is, a hard disk drive in the storage
unit) or the storage adapter that is attached to the storage unit. The failing server might be part of a cluster
if any of the following conditions is true:
– You have identified the failing server as part of a cluster (two or more servers sharing external storage
devices).
– One or more external storage units are attached to the failing server and at least one of the attached
storage units is also attached to another server or unidentifiable device.
– One or more servers are located near the failing server.
Important: If the server is part of a shared HDD cluster, run one test at a time. Do not run any suite of
tests, such as “quick” or “normal” tests, because this might enable the hard disk drive diagnostic tests.
• If the server is halted and a POST error code is displayed, see Appendix B “UEFI (POST) error codes” on
page 441. If the server is halted and no error message is displayed, see “Troubleshooting by symptom” on
page 61 and “Solving undetermined problems” on page 74.
• For information about power-supply problems, see “Solving power problems” on page 72, “Power
problems” on page 70, and “Power-supply LEDs” on page 54.
• For intermittent problems, check the event log; see “Event logs” on page 56 and Appendix C “DSA
diagnostic test results” on page 451.
Performing the checkout procedure

To perform the checkout procedure, do the following:
Step 1. Is the server part of a cluster?

• No: Go to Step 2 on page 51.

• Yes: Shut down all failing servers that are related to the cluster. Go to Step 3 on page 51.
Step 2. Do the following:
a. Check the power supply LEDs. See “Power-supply LEDs” on page 54.
b. Turn off the server and all external devices.
c. Check all internal and external devices for compatibility at http://www.lenovo.com/
serverproven/.
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 61.
h. Check the system-error LED on the operator information panel. If it is lit, check the light path
diagnostics LEDs. See “Light path diagnostics” on page 53.
i. Check for the following results:
• Successful completion of the POST (see “POST” on page 58)
• Successful completion of startup, which is indicated by a readable display of the operating-
system desktop
Step 3. Is there a readable image on the monitor screen?
• No: Find the failure symptom in “Troubleshooting by symptom” on page 61; if necessary, see
“Solving undetermined problems” on page 74.
• Yes: Run DSA. See “Running DSA Preboot diagnostic program” on page 59.
– If DSA reports an error, follow the instructions in Appendix C “DSA diagnostic test results” on
page 451.
– If DSA does not report an error but you still suspect a problem, see “Solving undetermined
problems” on page 74.
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related problems.
• Light path diagnostics

Use light path diagnostics to diagnose system errors quickly. For more information, see “Light path
diagnostics” on page 53.
• Event logs
The event logs list the error codes and messages that are generated when an error is detected. For more
information, see “Event logs” on page 56.
The Integrated Management Module 2.1 (IMM2.1) combines service processor functions, video controller,
and remote presence and blue-screen capture features in a single chip. The IMM2.1 provides advanced
service-processor control, monitoring, and alerting function. If an environmental condition exceeds a
threshold or if a system component fails, the IMM2.1 lights LEDs to help you diagnose the problem,
records the error in the IMM2.1 event log, and alerts you to the problem. Optionally, the IMM2.1 also
provides a virtual presence capability for remote server management capabilities. The IMM2.1 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 2.1 (IMM2.1), see “Using the Integrated
Management Module 2.1 (IMM2.1)” on page 35, Appendix A “Integrated Management Module 2.1
(IMM2.1) error messages” on page 173, and the Integrated Management Module II User's Guide at http://
publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.sysx.imm2.doc/ product_
page.html.
• Dynamic System Analysis Preboot (DSA Preboot)
The DSA Preboot diagnostic program is stored in the integrated USB memory on the server. DSA Preboot
collects and analyzes system information to aid in diagnosing server problems, as well as offering a rich
set of diagnostic tests for the major server components. DSA Preboot collects the following information
about the server:
– Drive health information
– IMM2.1 configuration information
– IMM2.1 environmental information
– Installed hardware, including PCI and USB information
– Light path diagnostics status
– Microprocessor, input/output hub, and UEFI error logs
– Network interfaces and settings
– Option card driver and firmware information
– RAID controller configuration
– Service processor (Integrated Management Module 2.1 (IMM2.1)) status and configuration
– System configuration
– Vital product data, firmware, and UEFI configuration
DSA Preboot also provides diagnostics for the following system components (when they are installed):
– Emulex Ethernet controller
– IMM2.1 I2C bus
– Light path diagnostics panel
– Memory modules
– Microprocessors
– Optical devices (CD or DVD)
– SAS or SATA drives
– LSI controller
– Broadcom Ethernet controller
– FusionIO storage
– Intel GPU
– NVIDIA GPU
For more information about running DSA Preboot on the server, see “Running DSA Preboot diagnostic
program” on page 59.
You can also diagnose and solve problems by symptom. For more information, see “Troubleshooting by
symptom” on page 61.

• Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
• If an action step is preceded by '(Trained technician only)', that step must be performed only by a trained
technician.
• Go to the Lenovo support Web site at http://www.lenovo.com/support to check for technical information,
hints, tips, and new device drivers or to submit a request for information.
Light path diagnostics

Light path diagnostics is a system of LEDs on various external and internal components of the server that
leads you to the failed component. When an error occurs, LEDs are lit along the path of the front panel, the
operator information panel, then on the failed component. By viewing the LEDs in a particular order, you can
often identify the source of the error.
When LEDs are lit to indicate an error, they remain lit when the server is turned off, if the server is still
connected to power and the power supply is operating correctly.
Before you work inside the server to view light path diagnostics LEDs, read the safety information “Safety” on
page v and “Handling static-sensitive devices” on page 94.
If an error occurs, view the light path diagnostics LEDs and look at the operator information panel on the
front of the server.
The following table describes the LEDs on the operator information panel and suggested actions to correct
the detected problems.
Table 5. Light path diagnostics: LED status and actions
LED Description Action

This LED is used as a presence detection Use this LED to locate the server among
System-locator LED LED. You can use Systems Director or other servers visually.
(blue) IMM2.1 to light this LED remotely.
LED on: An error has occurred and cannot 1. Check the IMM2.1 event log and the
Check log LED be isolated without performing certain system-error log for information about
(amber) procedures. the error.
2. Save the log if necessary and clear the
log afterward.
LED on: An error has occurred. 1. Check the system-locator LED and
System-error LED
check log LED and follow the
(amber)
instructions.
2. Check the IMM2.1 event log and the
system-error log for information about
the error.
3. Save the log if necessary and clear the
log afterward.
Error LEDs
This section describes the error LEDs on the system board and the suggested actions to correct the
detected problems.
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 “Dynamic System Analysis” on page 58.
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 the lit system-error LED on the operator information panel 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 v and “Handling static-
sensitive devices” on page 94.
If an error occurs or you suspect a system error, do the following:

1. Check the operator information panel on the front of the server. If the system-error LED is lit, it confirms
that an error has occurred.
2. Check the IMM2.1 event log and the system-error log for information about the error.
3. Look at the system service label inside the cover of the server, which gives an overview of internal
components. This label also usually includes helpful instructions to help you correct the error.
For the locations of the error LEDs, see “System-board LEDs” on page 23.
The following table describes the LEDs on the system board and suggested actions to correct the detected
problems:
• IMM2.1 heartbeat LED: When the server is connected to power, this LED flashes quickly to indicate that
the IMM2.1 code is loading. When the loading is completed, the LED stops flashing quickly and then
flashes slowly, which means that the IMM2.1 if fully operational and you can press the power-control
button to start the server.
If the LED does not begin flashing within 30 seconds after the server is connected to power, do the
following:
1. (Trained technician only) Recover the firmware. See “Recovering the server firmware (UEFI update
failure)” on page 76.
2. (Trained technician only) Replace the system board.
• System-error LED: When the LED is lit, it indicates that the microprocessor VRD and/or power voltage
regulators have failed. Then, you need to ask trained technician to replace the system board.
• CPLD heartbeat LED: If the LED flashes at 1 Hz, it is functioning properly and no action is necessary. If the
LED is not flashing, replace the system board (Trained technician only).
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:

• One microprocessor
• One 4 GB DIMM
• Power supply

• Power cord
• Four cooling fans
For the locations of the LEDs and connectors on the rear of the server, see “Rear view” on page 17.
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 6. Power-supply LEDs
ac dc power Power-supply Description Action

power LED error LED
LED
On On Off Normal operation No action needed.
Off Off Off No ac power to the 1. Check the ac power to the server.
server or a problem
with the ac power 2. Make sure that the power cord is connected to a
source. functioning power source.
This symptom is a 3. Restart the server. If the error remains, check
normal condition the power-supply LEDs.
when no ac power
is present. 4. If the problem remains, replace the power-
supply.
On Off Off Faulty system 1. Turn off the server and disconnect the power
board or faulty cord from the server; then, reconnect the power
power supply cord.
The symptom
typically indicates 2. If the system board error (fault) LED is not lit,
that a power supply replace the power supply.
is not fully seated. 3. (Trained technician only) If the system board
This is a normal error LED is lit, replace the system board.
condition before
turning on the
system.
On Off or On Faulty power Replace the power supply.

Flashing supply
On On On Power supply is Replace the power supply.

faulty but still
operational.
System pulse LEDs

This section describes the system pulse LEDs on the system board that monitors the system power-on and
power-off and boot progress.
The following LEDs are on the system board and monitor the system power-on and power-off sequencing
and boot progress. For the location of these LEDs, see “System-board LEDs” on page 23.
CPLD heartbeat LED: If the LED flashes at 1 Hz, it is functioning properly and no action is necessary. If the
LED is not flashing, replace the system board (Trained technician only).
IMM2.1 heartbeat LED: The LED status shows the following different stages of the IMM2.1 heartbeat
sequencing process:
1. When this LED is blinking fast (approximately 4 Hz), this indicates that the IMM2.1 code is in the loading
process.
2. When this LED goes off momentarily, this indicates that the IMM2.1 code has loaded completely.
3. When this LED goes off momentarily and then starts blinking slowing (approximately 1 Hz), this indicates
that IMM2.1 is fully operational. You can now press the power-control button to power on the server.
4. (Trained technician only) If this LED does not blink within 30 seconds of connecting a power source to
the server, replace the system board.
Event logs
Error codes and messages are recorded in various event logs, including the POST event log, system-event
log, Integrated Management Module 2.1 (IMM2.1) event log, and DSA event log.
• POST event log: This log contains the most recent error codes and messages that were generated during
the POST. You can view the contents of the POST event log from Setup Utility. See “Starting the Setup
Utility program” on page 29. For more information about POST error codes, see Appendix B “UEFI (POST)
error codes” on page 441.
• 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 2.1 (IMM2.1). You can view the contents of the system-event log through 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 2.1 (IMM2.1) error messages” on page 173.
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 and down arrow keys.
Some IMM2.1 sensors cause assertion events to be logged when their setpoints are reached. When a
setpoint condition no longer exists, a corresponding event is logged. However, not all events are
assertion-type events.
• Integrated Management Module 2.1 (IMM2.1) event log: This log contains a filtered subset of all
IMM2.1, POST, and system management interrupt (SMI) events. You can view the IMM2.1 event log
through the IMM2.1 Web interface. For more information, see “Logging in to the Web interface” on page
37. You can also view the IMM2.1 event log through the Dynamic System Analysis (DSA) Preboot program
(as the ASM event log). For more information about IMM2.1 error messages, see Appendix A “Integrated
Management Module 2.1 (IMM2.1) error messages” on page 173.
• DSA event log: This log is generated by the Dynamic System Analysis (DSA) Preboot program, and it is a
chronologically ordered merge of the system-event log (as the IPMI event log), the IMM2.1 chassis-event
log (as the ASM event log). For more information about DSA and DSA messages, see “Dynamic System
Analysis” on page 58 and Appendix C “DSA diagnostic test results” on page 451.
Viewing event logs through Setup Utility

To view the POST event log or system-event log after starting the server, do the following:

Step 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.
Step 3. Select System Event Log and do one of the following:
• To view the POST event log, select POST Event Viewer.
• To view the system-event log, select System Event Log.

Viewing event logs without restarting the server
If the server is not hung and the IMM2.1 is connected to a network, methods are available for you to view one
or more event logs without having to restart the server.
If you have installed Lenovo XClarity Essentials OneCLI, you can use it to view the system-event log (as the
IPMI event log), or the IMM2.1 event log (as the Chassis event log), the operating-system event logs, or the
merged OneCLI log. You can also use DSA Preboot to view these logs, although you must restart the server.
To install OneCLI or check for and download a later version of DSA Preboot CD image, go to: https://
support.lenovo.com/us/en/documents/LNVO-DSA.
If IPMItool is installed in the server, you can use it to view the system-event log. Most recent versions of the
Linux operating system come with a latest version of IPMItool. For an overview of IPMI, go to http://
www.ibm.com/developerworks/linux/blueprints/ and click Using Intelligent Platform Management Interface
(IPMI) on Lenovo Linux platforms.
You can view the IMM2.1 event log through the Event Log link in the Integrated Management Module 2.1
(IMM2.1) Web interface. For more information, see “Logging in to the Web interface” on page 37.
The following table describes the methods that you can use to view the event logs, depending on the
condition of the server. The first three conditions generally do not require that you restart the server.
Table 7. Methods for viewing event logs
Condition Action
The server is not hung and is Use any of the following methods:
connected to a network (using an • Run Lenovo XClarity Essentials OneCLI to view the system event log
operating system controlled network (requires IPMI driver) or create an output file that you can send to Lenovo
ports). service and support (using ftp or local copy).
• Use IPMItool to view the system-event log (requires the IPMI driver).
• Use the Web browser interface to the IMM2.1 to view the system-event log
locally (requires RNDIS USB LAN driver).
The server is not hung and is not • Run Lenovo XClarity Essentials OneCLI to view the system event log
connected to a network (using an (requires IPMI driver) or create an output file that you can send to Lenovo
operating system controlled network service and support (using ftp or local copy).
ports). • Use IPMItool to view the system-event log (requires the IPMI driver).
• Use the Web browser interface to the IMM2.1 to view the system-event log
locally (requires RNDIS USB LAN driver).
The server is not hung and the In a Web browser, type the IP address for the IMM2.1 and go to the Event
Integrated Management Module 2.1 Log page. For more information, see “Obtaining the IMM2.1 host name” on
(IMM2.1) is connected to a network. page 36 and “Logging in to the Web interface” on page 37.
The server is hung, and no • If DSA Preboot is installed, restart the server and press F2 to start DSA
communication can be made with the Preboot and view the event logs. For more information, see “Running DSA
IMM2.1. Preboot diagnostic program” on page 59.
• Alternatively, you can restart the server and press F1 to start the Setup
Utility and view the POST event log or system-event log. For more
information, see “Viewing event logs through Setup Utility” on page 56.
Clearing the event logs

To clear the event logs, do the following:
Note: The POST error log is automatically cleared each time the server restarts.
Step 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.
Step 3. To clear the IMM2.1 system-event log, select System Event Log ➙ Clear System Event Log,
then, press Enter twice.
POST
When you turn on the server, it performs a series of tests to check the operation of the server components
and some optional devices in the server. This series of tests is called power-on self-test, or POST.
Note: You cannot view the server status through beep codes.
If a power-on password is set, you must type the password when required and then press Enter to allow the
POST to start running.
If a problem is detected during the POST, an error message is displayed on the screen and also sent to the
POST event log. For more information, see Appendix B “UEFI (POST) error codes” on page 441.
If POST detects a problem, an error message is sent to the POST event log. For more information, see “Event
logs” on page 56.
Dynamic System Analysis

Dynamic System Analysis (DSA) collects and analyzes system information to aid in diagnosing server
problems. Lenovo provides DSA Preboot edition to users.
LXCE OneCLI collects and analyzes system information to aid in diagnosing server problems. OneCLI runs
on the server operating system and collects the following information about the server:
• Drive health information
• Event logs for ServeRAID controllers and service processors
• Hardware inventory, including PCI and USB information
• Light path diagnostics status
• Network interfaces and settings
• Performance data and details about processes that are running
• RAID controller configuration
• Service processor (Integrated Management Module 2.1 (IMM2.1)) status and configuration
• System configuration
• Vital product data and firmware information
For system-specific information about the action that you should take as a result of a message that DSA
generates, see Appendix C “DSA diagnostic test results” on page 451.
If you cannot find a problem by using DSA, see “Solving undetermined problems” on page 74 for information
about testing the server.
Note: DSA Preboot might appear to be unresponsive when you start the program. This is normal symptom
while the program loads.
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 medium such as a CD or DVD using Lenovo

XClarity Essentials Bootable Media Creator (BoMC). For more details, refer to the BoMC user guide. You can
download the user guide at:
https://support.lenovo.com/ us/en/documents/LNVO-BOMC
DSA Preboot includes diagnostic routines that would be disruptive to run within the operating-system
environment (such as resetting devices). 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 Ethernet controller
• Optical devices (CD or DVD)
• Tape drives (SCSI, SAS, or SATA)
• Memory
• Microprocessor
• Checkpoint panel
• I2C bus
• SAS and SATA drives
If you are able to restart the server or if you need comprehensive diagnostics, use DSA Preboot.
For more information and to download DSA Preboot, go to:

https://support.lenovo.com/us/ en/documents/LNVO-DSA
Running DSA Preboot diagnostic program

Note: The DSA memory test might take up to 30 minutes to finish. If the problem is not a memory problem,
skip the memory test.
To run the DSA Preboot diagnostic program, do the following:
Step 1. If the server is running, turn off the server and all attached devices.
Step 2. Turn on all attached devices; then, turn on the server.
Step 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 symptom while the program loads. The
loading process might take up to 10 minutes.
Step 4. Optionally, select Quit to DSA to exit from the stand-alone memory diagnostic program.
Note: After you exit the stand-alone memory diagnostic environment, you must restart the server
to access the stand-alone memory diagnostic environment again.
Step 5. Type gui to display the graphical user interface, or type cmd to display the DSA interactive menu.
Step 6. Follow the instructions on the screen to select the diagnostic tests to run.
If the diagnostic program does not detect any hardware errors but the problem remains during normal server
operation, the diagnostic program error might be the cause. If you suspect a diagnostic program error, see
the information that comes with your program.
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 is hung 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 is hung.
Diagnostic text messages

Diagnostic text messages are displayed while the tests are running.
A diagnostic text message contains one of the following results:
Passed: The test was completed without any errors.
Failed: The test detected an error.
Aborted: The test could not proceed because of the server configuration.
Additional information concerning test failures is available in the extended diagnostic results for each test.
Viewing the test log results and transferring the DSA collection
To view the test log for the results when the tests are completed, do one of the following:
• Click the Success link in the Status column, if you are running the DSA graphical user interface.
• Type :x to exit the Execute Tests menu, if you are running the DSA interactive menu. Then, select
completed tests to view the results.
• Select Diagnostic Event Log in the graphical user interface.
To transfer DSA Preboot collections to an external USB device, type the copy command in the DSA
interactive menu.
You can also send the DSA error log to Lenovo service and support to aid in diagnosing the server problems.
Automated service request (call home)

Lenovo provides a tool that can automatically collect and send data or call Lenovo Support when an error is
detected.
This tool can help Lenovo Support speed up the process of diagnosing problems.
Electronic Service Agent

Electronic Service Agent™ monitors, tracks, and captures system hardware errors as well as hardware and
software inventory information. It also reports serviceable problems directly to Lenovo Support.
Although you can collect these system data manually, Electronic Service Agent could also be a good
alternative because it uses minimal system resources and can be easily downloaded from http://www-
01.ibm.com/support/esa/.
Error messages
Lenovo provide error messages on the Web site and PDF file. If you are viewing the Web site, the list of error
codes and messages for UEFI/POST, IMM2.1, and DSA that are generated when a problem is detected will
display.
If you are viewing PDF file, refer to the following topics:

• Appendix A “Integrated Management Module 2.1 (IMM2.1) error messages” on page 173

• Appendix B “UEFI (POST) error codes” on page 441
• Appendix C “DSA diagnostic test results” on page 451
Troubleshooting by symptom
Use the troubleshooting tables to find solutions to problems that have identifiable symptoms.
If you cannot find a solution to the problem in these tables, see Appendix C “DSA diagnostic test results” on
page 451 for information about testing the server and “Running DSA Preboot diagnostic program” on page
59 for additional information about running the DSA Preboot program. For additional information to help you
solve problems, see “Start here” on page 47.
Notes:
• Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
• If an action step is preceded by '(Trained technician only)', that step must be performed only by a trained
technician.
• Go to the Lenovo support Web site at http://www.lenovo.com/support to check for technical information,
hints, tips, and new device drivers or to submit a request for information.
If you have added new software or a new optional device and the server is not working, do the following
before you use the troubleshooting tables:
Step 1. Check the system-error LED on the operator information panel; if it is lit, check the light path
diagnostics LEDs (see “Light path diagnostics” on page 53).
Step 2. Remove the software or device that you just added.
Step 3. Run Dynamic System Analysis (DSA) to determine whether the server is running properly (see
Appendix C “DSA diagnostic test results” on page 451).
Step 4. Reinstall the new software or new device.
General problems
Table 8. General symptoms and actions
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 See “Nx-boot failure” on page 77 and “Recovering the server firmware (UEFI update
screen is on. You cannot start failure)” on page 76.
Setup Utility by pressing F1.
Optical drive problems
Table 9. Optical drive symptoms and actions
Symptom Action
The optical drive is not 1. Make sure that:
recognized.
• The SATA connector to which the optical drive is attached (primary or
secondary) is enabled in Setup Utility.
• All cables and jumpers are installed correctly.
• The correct device driver is installed for the optical drive.
2. Run the optical drive diagnostic programs.
3. Reseat the following components:
a. Optical drive
b. Optical drive cable
4. Replace the components listed in step 3 one at a time, in the order shown,
restarting the server each time.
A CD or DVD is not working 1. Clean the CD or DVD.

properly.
2. Replace the CD or DVD with new CD or DVD media.
3. Run the optical drive diagnostic programs.
4. Check the connector and signal cable for bent pins or damage.
5. Reseat the optical drive.
6. Replace the optical drive.
The optical drive tray is not 1. Make sure that the server is turned on.
working.
2. Insert the end of a straightened paper clip into the manual tray-release hole.
3. Reseat the optical drive.
4. Replace the optical drive.
Hard disk drive problems

Table 10. Hard disk drive symptoms and actions
Symptom Action
Not all drives are recognized Remove the drive that is indicated by the diagnostic tests; then, run the hard disk
by the hard disk drive drive diagnostic test again. If the remaining drives are recognized, replace the drive
diagnostic test. that you removed with a new one.
The server stops responding Remove the hard disk drive that was being tested when the server stopped
during the hard disk drive responding, and run the diagnostic test again. If the hard disk drive diagnostic test
diagnostic test. runs successfully, replace the drive that you removed with a new one.
A hard disk drive was not Reseat all hard disk drives and cables; then, run the hard disk drive diagnostic test.
detected while the operating
system was being started.
A hard disk drive passes the Run the diagnostic SCSI Fixed Disk Test. See “Running DSA Preboot diagnostic
diagnostic Fixed Disk Test, but program” on page 59.
the problem remains. Note: This test is not available on servers that have RAID arrays or servers that have
SATA hard disk drives.

Table 10. Hard disk drive symptoms and actions (continued)
Symptom Action
A hard disk drive has failed, 1. Reconfigure the integrated SAS/SATA controller with RAID capabilities and the
and the associated yellow hard devices that are attached to it.
disk drive status LED is lit.
(hot-swap hard disk drives) 2. Run the DSA disk drive test. See “Dynamic System Analysis” on page 58.
3. If the drive fails the test, replace the drive.
A newly installed hard disk 1. Observe the associated yellow hard disk drive status LED. If the LED is lit, it
drive is not recognized. 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:
• 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.
• 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.
• If neither LED is lit or flashing, check the hard-disk-drive backplane (go to
step 4).
• 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. Suspect the backplane signal cable or the backplane:
• Replace the affected backplane signal cable.
• Replace the affected backplane.
8. Run the DSA tests for the SAS/SATA adapter and hard disk drives. See
“Dynamic System Analysis” on page 58.
• If the adapter passes the test but the drives are not recognized, replace the
backplane signal cable and run the tests again.
• Replace the backplane.
• If the adapter fails the test, disconnect the backplane signal cable from the
adapter and run the tests again.
• If the adapter fails the test, replace the adapter.
9. See “Problem determination tips” on page 74.
Multiple hard disk drives fail. Make sure that the hard disk drive, RAID card, 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.
Table 10. Hard disk drive symptoms and actions (continued)
Symptom Action
Multiple hard disk drives are 1. Review the storage subsystem logs for indications of problems within the
offline. storage subsystem, such as backplane or cable problems.
A replacement hard disk drive 1. Make sure that the hard disk drive is recognized by the adapter (the green hard
does not rebuild. 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 use,
LED does not accurately run the DSA disk drive test. See “Dynamic System Analysis” on page 58.
represent the actual state of
the associated drive. (hot- 2. Use one of the following procedures:
swap hard disk drives) • If the drive passes the test, replace the backplane.
• If the drive fails the test, replace the drive.
A yellow hard disk drive status 1. If the yellow hard disk drive LED and the RAID card software do not indicate the
LED does not accurately same status for the drive, do the following:
represent the actual state of
the associated drive. (hot- a. Turn off the server.
swap hard disk drives) b. Reseat the SAS/SATA adapter.
c. Reseat the backplane signal cable and power cable.
d. Reseat the hard disk drive.
e. Turn on the server and observe the activity of the hard disk drive LEDs.
Hypervisor problems
Table 11. Hypervisor symptoms and actions
Symptom Action
If an optional embedded 1. Make sure that the optional embedded hypervisor flash device is selected on
hypervisor flash device is not the boot manager <F12> Select Boot Device at startup.
listed in the expected boot
order, does not appear in the 2. Make sure that the embedded hypervisor flash device is seated in the connector
list of boot devices, or a similar correctly. See “Removing a USB embedded hypervisor flash device” on page
problem has occurred. 120 and “Installing a USB embedded hypervisor flash device” on page 121.
3. See the documentation that comes with the optional embedded hypervisor flash
device for setup and configuration information.
4. Make sure that other software works on the server.

Intermittent problems
Table 12. Intermittent problems and actions
Symptom Action
A problem occurs only 1. Make sure that:
occasionally and is difficult to • All cables and cords are connected securely to the rear of the server and
diagnose. attached devices.
• When the server is turned on, air is flowing from the fan grille. If there is no
airflow, the fan is not working. This can cause the server to overheat and shut
down.
2. Check the system-error log or IMM2.1 event log. See “Event logs” on page 56.
Keyboard, mouse, or USB-device problems

Table 13. Keyboard, mouse, or USB-device symptoms and actions
Symptom Action
All or some keys on the 1. Make sure that:
keyboard do not work. • The keyboard cable is securely connected.
• The server and the monitor are turned on.
2. Run the Setup Utility and enable the USB device option.
3. If the keyboard t is connected to a USB hub, disconnect the keyboard from the
hub and connect it directly to the server.
4. Replace the keyboard.
The mouse or USB-device 1. Make sure that:

does not work.
• The mouse or USB device cable is securely connected to the server.
• The mouse or USB device drivers are installed correctly.
• The server and the monitor are turned on.
• The mouse option is enabled in the Setup Utility.
2. If you are using a USB mouse or USB device and it is connected to a USB hub,
disconnect the mouse or USB device from the hub and connect it directly to the
server.
3. Replace the mouse or USB device.
Memory problems
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.
Table 14. Memory problems and actions
Symptom Action
The amount of system memory 1. Make sure that:
that is displayed in Setup
Utility is less than the amount • No error LEDs are lit on the operator information panel.
of installed physical memory. • No DIMM error LEDs are lit on the system board.
• The memory modules are seated correctly.
• You have installed the correct type of memory.
• If you changed the memory, you updated the memory configuration in the
Setup Utility.
• 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.
• 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:
• If a DIMM was disabled by a system-management interrupt (SMI), replace the
DIMM.
• If a DIMM was disabled by the user or by the 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 program” on page 59.
5. Add one pair of DIMMs at a time, making sure that the DIMMs in each pair
match.
6. Reseat the DIMM.
7. Re-enable all DIMMs using the Setup Utility, and then restart the server.
8. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. DIMMs
b. (Trained technician only) system board
Multiple rows of DIMMs in a 1. Reseat the DIMMs; then, restart the server.
branch are identified as failing.
2. Replace the failing DIMM.
3. (Trained technician only) Replace the system board
A memory error occurs For example, if you suspect memory module in slot 1 or slot 2 is failing, do the
indicating that one memory following:
module in a channel is failing. 1. Exchange memory module in slot 1 with memory module in slot 3.
2. Restart the server.
3. Check whether this error still occurs.
a. If yes, it means that memory module in slot 2 is failing. Then, replace
memory module in slot 2 with a new memory module.
b. If no, it means that memory module in slot 1 is failing. Then, replace memory
module in slot 1 with a new memory module.
For more information, refer to the tip files at:

Monitor problems
Some Lenovo 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 15. Monitor and video symptoms and actions
Symptom Action
Testing the monitor. 1. Make sure that the monitor cables are firmly connected.
2. Try using a different monitor on the server, or try using the monitor that is being
tested on a different server.
3. Run the diagnostic programs. If the monitor passes the diagnostic programs,
the problem might be caused by a video device driver.
The screen is blank. 1. If the server is attached to a KVM switch, bypass the KVM switch to eliminate it
as a possible cause of the problem: connect the monitor cable directly to the
correct connector on the rear of the server.
2. Make sure that:
• The server is turned on. If there is no power to the server, see “Power
• The monitor cables are connected correctly.
• The monitor is turned on and the brightness and contrast controls are
adjusted correctly.
• 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 25.
5. Observe the checkpoint LEDs on the system board; if the codes are changing,
go to the next step.
a. Monitor
b. Video adapter (if one is installed)
c. (Trained technician only) System board
The monitor works when you 1. Make sure that:

turn on the server, but the
screen goes blank when you • The application program is not setting a display mode that is higher than the
start some application capability of the monitor.
programs. • You installed the necessary device drivers for the application.
2. Run video diagnostics. See “Running DSA Preboot diagnostic program” on
page 59.
• If the server passes the video diagnostics, the video is good. Then, you can
refer to “Solving undetermined problems” on page 74.
• (Trained technician only) If the server fails the video diagnostics, replace the
system board.
Table 15. Monitor and video symptoms and actions (continued)
Symptom Action
The monitor has screen jitter, 1. If the monitor self-tests show that the monitor is working properly, consider the
or the screen image is wavy, 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 inches) apart, and turn on
the monitor.
Note: Non-Lenovo monitor cables might cause unpredictable problems.

2. Reseat the monitor and cable.
a. Monitor
b. (Trained technician only) System board
Wrong characters appear on 1. If the wrong language is displayed, update the server firmware to the latest level
the screen. (see “Updating the firmware” on page 25) with the correct language.
2. Reseat the monitor and cable.
a. Monitor
b. (Trained technician only) System board
Network connection problems

Table 16. Network connection problems and actions
Symptom Action
Login failed by using LDAP 1. Make sure that the license key is valid.
account with SSL enabled.
2. Generate a new license key and log in again.

Optional-device problems
Table 17. Optional-device problems and actions
Symptom Action
A Lenovo optional device that 1. Make sure that:
was installed does not work. • The device is designed for the server. Go to:
• You followed the installation instructions that came with the device and the
device is installed correctly.
• You have not loosened any other installed devices or cables.
• You updated the configuration information in the Setup Utility. Whenever
memory or any other device is changed, you must update the configuration.
2. Reset the device that you installed.
3. Replace the device that you installed.
A Lenovo optional device that 1. Make sure that all of the cable connections for the device are secure.
worked previously does not
work now. 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.
Operating system boot problem

Table 18. Operating system boot problem and action
Symptom Action
You cannot boot automatically To recreate the boot entry manually, do the following:
in the following operating 1. Turn on the server and press F1 to enter Setup Utility.
systems:
2. Select Boot manager.
• SUSE Linux® Enterprise
Server 11 with Service Pack 3. Select Add Boot Option.
1 4. Select the boot entry with the string “*.efi”
• Red Hat® Enterprise Linux 6 5. Type the description such as “OS_Install”. Then, select Commit Changes.
For more information, refer to the tip files at:
Power problems
Table 19. Power problems and actions
Symptom Action
The power-control button does 1. Disconnect the server power cords.
not work, and the reset button
does not work (the server does 2. Reconnect the power cords.
not start). 3. (Trained technician only) Reseat the operator information panel cable, and then
repeat steps 1a and 1b.
Note: The power-control
button will not function until • (Trained technician only) If the server starts, reseat the operator information
approximately 20 seconds panel. If the problem remains, replace the operator information panel.
after the server has been • If the server does not start, bypass the power-control button by using the
connected to power. force power-on jumper. See “System-board switches and jumpers” on page
21. If the server starts, reseat the operator information panel. If the problem
remains, replace the operator information panel.
4. Make sure that:
a. The power cords are correctly connected to the server and to a working
electrical outlet.
b. The type of memory that is installed is correct.
c. The DIMM is fully seated.
d. The LEDs on the power supply do not indicate a problem.
a. DIMMs
b. (Trained technician only) Power-supply cables to all internal components
c. (Trained technician only) Power switch connector
a. DIMMs
b. Power supply
7. If you installed an optional device, remove it, and restart the server. If the server
now starts, you might have installed more devices than the total devices that
power supply could support.
8. See “Power-supply LEDs” on page 54.
The server does not turn off. 1. Determine whether you are using an Advanced Configuration and Power
Interface (ACPI) or a non-ACPI operating system. If you are using a non-ACPI
operating system, do the following:
a. Press Ctrl+Alt+Delete.
b. Turn off the server by pressing the power-control button for five seconds.
c. Restart the server.
d. If the server fails the POST and the power-control button does not work,
disconnect the power cord for five seconds; then, reconnect the power cord
and restart the server.
2. If the problem remains or if you are using an ACPI-aware operating system,
suspect the system board.
The server unexpectedly shuts See “Solving undetermined problems” on page 74.
down, and the LEDs on the
operator information panel are
not lit.

Serial port problems
Table 20. Serial port problems and actions
Symptom Action
The number of serial ports that 1. Make sure that:
are identified by the operating • Each port is assigned a unique address in the Setup Utility and none of the
system is less than the number serial ports are disabled.
of installed serial ports. • The serial-port adapter (if one is present) is seated correctly.
2. Reseat the serial port adapter.
3. Replace the serial port adapter.
A serial device does not work. 1. Make sure that:

• The device is compatible with the server.
• The serial port is enabled and is assigned a unique address.
• The device is connected to the correct connector.
a. Failing serial device
b. Serial cable
a. Failing serial device
b. Serial cable
ServerGuide problems
Table 21. ServerGuide problems and actions
Symptom Action
The ServerGuide Setup and 1. Make sure that the server supports the ServerGuide program and has a
Installation CD will not start. startable (bootable) DVD drive.
2. If the startup (boot) sequence settings have been changed, make sure that the
DVD drive is the 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 ServeRAID Manager 1. Make sure that the hard disk drive is connected correctly.
program cannot view all
installed drives, or the 2. Make sure that the SAS hard disk drive cables are securely connected.
operating system cannot be
installed.
The operating-system Make more space available on the hard disk.
installation program
continuously loops.
The ServerGuide program will Make sure that the operating-system CD is supported by the ServerGuide program.
not start the operating-system For a list of supported operating-system versions, go to https://support.lenovo.com/
CD. solutions/lnvo-toolkit, click the link for your ServerGuide version, and scroll down to
the list of supported Microsoft Windows operating systems.
The operating system cannot Make sure that the server supports the operating system. If it does, either no logical
be installed; the option is not drive is defined (SCSI RAID servers), or the ServerGuide System Partition is not
available. present. Run the ServerGuide program and make sure that setup is complete.
Software problems
Table 22. Software problems and actions
Symptom Action
You suspect a software 1. To determine whether the problem is caused by the software, make sure that:
problem. • 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 installed an adapter or a memory module, the server might have a
memory-address conflict.
• The software is designed to operate on the server.
• Other software works on the server.
• 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.
USB connector problems

Table 23. USB connector problems and actions
Symptom Action
A USB device does not work. 1. Make sure that:
• The correct USB device driver is installed.
• The operating system supports USB devices.
2. Make sure that the USB configuration options are set correctly in the Setup
Utility. For more information, see “Using the Setup Utility program” on page 29.
3. If you are using a USB hub, disconnect the USB device from the hub and
connect it directly to the server.
Chipset driver installation problems

Table 24. Chipset driver installation problems and actions
Symptom Action
For servers installed with the Install the driver for the Intel Rapid Storage Technology enterprise (RSTe) NVMe
Windows operating system, driver.
after you install all the chipset
drivers, a yellow exclamation To download the driver, go to:
mark is still displayed for the http://support.lenovo.com/us/en/products/Servers/Lenovo-x86-servers/
PCI device in the Device Lenovo-System-x3250-M6/3633/downloads/DS120488
Manager window.
Note: There is no impact on the server function if you do not install this driver.
Solving power problems

Power problems can be difficult to solve. For example, a short circuit can exist anywhere on any of the power
distribution buses. Usually, a short circuit will cause the power subsystem to shut down because of an
overcurrent condition. To diagnose a power problem, use the following general procedure:
Step 1. Turn off the server and disconnect all power cords.

Step 2. Check for loose cables in the power subsystem. Besides, check for short circuits, for example, if a
loose screw is causing a short circuit on a circuit board.
Step 3. Turn on the server and check the lit LEDs on the system board. See “System-board LEDs” on page
23.
Step 4. Turn off the server and disconnect all power cords.
Step 5. Remove the adapters and disconnect the cables and power cords to all internal and external
devices until the server is at the minimum configuration that is required for the server to start. See
“Solving undetermined problems” on page 74.
Step 6. Reconnect all ac power cords and turn on the server. If the server starts successfully, turn off the
server, reseat the adapters, and then turn on the server. Repeat the operation to reseat other
devices one at a time until the problem is isolated.
If the server does not start from the minimum configuration, see “Power-supply LEDs” on page 54 to replace
the components in the minimum configuration one at a time until the problem is isolated.
Solving Ethernet controller problems

The method that you use to test the Ethernet controller depends on which operating system you are using.
For information about Ethernet controllers, see the Ethernet controller device-driver readme file and the
operating-system documentation.
Try the following procedures:
Step 1. Make sure that the correct device drivers, which come with the server, are installed and that they
are at the latest level.
Step 2. Make sure that the Ethernet cable is installed correctly.
• The cable must be securely attached at all connections. If the cable is attached but the problem
remains, try a different cable.
• If you set the Ethernet controller to operate at 100 Mbps, you must use Category 5 cabling.
• If you directly connect two servers (without a hub), or if you are not using a hub with X ports, use
a crossover cable. To determine whether a hub has an X port, check the port label. If the label
contains an X, the hub has an X port.
Step 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.
Step 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.
• The Ethernet link status LED is lit when the Ethernet controller receives a link pulse from the hub.
If the LED is off, there might be a defective connector or cable or a problem with the hub.
• The Ethernet transmit/receive activity LED is lit when the Ethernet controller sends or receives
data over the Ethernet network. If the Ethernet transmit/receive activity LED is off, make sure
that the hub and network are operating and that the correct device drivers are installed.
Step 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.
Step 6. Check for operating-system-specific causes of the problem.
Step 7. Make sure that the device drivers on the client and server are using the same protocol.
If the Ethernet controller still cannot connect to the network but the hardware appears to be working, the
network administrator must investigate other possible causes of the error.
Solving undetermined problems
If Dynamic System Analysis (DSA) cannot diagnose the failure or if the server is inoperative, use the
information in this section to solve the undetermined problems.
If you suspect that a software problem is causing failures (continuous or intermittent), see “Software
Corrupted data in CMOS memory or corrupted UEFI firmware can cause undetermined problems. To reset
the CMOS data, use the CMOS clear jumper (JP1) to clear the CMOS memory and override the power-on
password. See “System-board connectors” on page 21 for more information. If you suspect that the UEFI
firmware is corrupted, see “Recovering the server firmware (UEFI update failure)” on page 76.
If the power supplies are working properly, do the following:

Step 2. Make sure that the server is cabled correctly.
Step 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.
• Any external devices (such as printer, mouse, and non-Lenovo devices.
• Surge-suppressor device (on the server).
• Each adapter.
• Hard disk drives.
Note: The minimum configuration required for the server to start is one microprocessor and one 4
GB DIMM.
Step 4. Turn on the server. If the problem remains, suspect the following components in the following
order:
1. Power supply
2. Memory
3. Microprocessor
4. System board
If the problem is solved when you remove an adapter from the server but the problem recurs when you
reinstall the same adapter, suspect the adapter; if the problem recurs when you replace the adapter with a
different one, suspect the riser card.
If you suspect a networking problem and the server passes all the system tests, suspect a network cabling
problem that is external to the server.
Problem determination tips

Because of the variety of hardware and software combinations that can encounter, use the following
information to assist you in problem determination. If possible, have this information available when
requesting assistance from Lenovo.
The model number and serial number of the server are on the ID label attached on the front bezel.

Figure 14. ID label on the front of the server
• Machine type and model

• Microprocessor or hard disk drive upgrades
• Failure symptom
– Does the server fail the diagnostic tests?
– What occurs? When? Where?
– Does the failure occur on a single server or on multiple servers?
– Is the failure repeatable?
– Has this configuration ever worked?
– What changes, if any, were made before the configuration failed?
– Is this the original reported failure?
• Diagnostic program type and version level
• Hardware configuration (print screen of the system summary)
• UEFI firmware level
• IMM firmware level
• Operating system software
You can solve some problems by comparing the configuration and software setups between working and
nonworking servers. When you compare servers to each other for diagnostic purposes, consider them
identical only if all the following factors are the same in all the servers:
• Machine type and model
• UEFI firmware level
• IMM firmware level
• Adapters and attachments, in the same locations
• Address jumpers, terminators, and cabling
• Software versions and levels
• Diagnostic program type and version level
• Configuration option settings
• Operating-system control-file setup
For information about calling Lenovo for service, see Appendix D “Getting help and technical assistance” on
page 589.
Recovering the server firmware (UEFI update failure)
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.
If the server firmware has become corrupted, such as from a power failure during an update, you can recover
the server firmware in the following ways:
• In-band method: Recover server firmware, using either the boot block jumper (Automated Boot
Recovery) or a server firmware update package.
• Out-of-band method: Use the IMM2.1 Web interface to update the firmware and the latest server
firmware update package.
Note: You can obtain a server-firmware update package through one of the following ways:
• Search and download the update package from http://www.lenovo.com/support.
• Contact your Lenovo service representative. Phone numbers are available athttp://www.ibm.com/services
or http://www.ibm.com/planetwide.
The flash memory of the server consists of a primary bank and a backup bank. You must maintain a bootable
UEFI firmware image in the backup bank. If the server firmware in the primary bank becomes corrupted, you
can manually boot the backup bank with the UEFI boot backup jumper (JP16). In the case of image
corruption, this will occur automatically with the Automated Boot Recovery function.
In-band manual recovery method

To recover the server firmware and restore the server operation to the primary bank, do the following:
Step 1. Read “Safety” on page v and “Before removing or installing server components” on page 93.
Step 2. Turn off the server, and disconnect all power cords and external cables.
Step 3. Unlock and remove the server cover. See “Removing the server cover” on page 94.
Step 4. Locate the UEFI boot backup jumper on the system board. See “System-board switches and
jumpers” on page 21.
Step 5. Move the UEFI boot backup jumper from pins 1 and 2 to pins 2 and 3 to enable the UEFI recovery
mode.
Step 6. Reinstall the server cover; then, reconnect all power cords.
Step 7. Restart the server. The system begins the power-on self-test (POST).
Step 8. Boot the server to an operating system that is supported by the firmware update package that you
downloaded.
Step 9. Perform the firmware update by following the instructions that are in the firmware update package
readme file.
Step 10. Turn off the server and disconnect all power cords and external cables, and then remove the server
cover. See “Removing the server cover” on page 94.
Step 11. Move the UEFI boot backup jumper from pins 2 and 3 back to the primary position (pins 1 and 2).
Step 12. Reinstall the cover. See “Installing the server cover” on page 95.
Step 13. Reconnect the power cord and any cables that you removed.
Step 14. Turn on the server. The system begins the power-on self-test (POST). If this does not recover the
primary bank, continue with the following steps.

Step 15. Remove the server cover. See “Removing the server cover” on page 94.
Step 16. Reset the CMOS by removing the coin-cell battery. See “Removing the coin-cell battery” on page
128.
Step 17. Leave the coin-cell battery out of the server for approximately 5 to 15 minutes.
Step 18. Reinstall the coin-cell battery. See “Installing the coin-cell battery” on page 129.
Step 19. Reinstall the cover. See “Installing the server cover” on page 95.
Step 20. Reconnect the power cord and any cables that you removed.
Step 21. Turn on the server. The system begins the power-on self-test (POST).
Step 22. If these recovery efforts fail, contact your Lenovo service representative for support.
In-band automated boot recovery method

Note: Use this method there is a log entry or Booting Backup Image displayed on the firmware splash screen;
otherwise, use the in-band manual recovery method.
Before the automated boot recovery process starts, observe the following:
• Boot the server to an operating system that is supported by the firmware update package that you
downloaded.
• Perform the firmware update by following the instructions that are in the firmware update package readme
file.
Out-of-band method
See the IMM2.1 documentation (Integrated Management Module II User's Guide) at http://
publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.sysx.imm2.doc/ product_
page.html.
Automated boot recovery (ABR)

While the server is starting, if the integrated management module II detects problems with the server
firmware in the primary bank, the server automatically switches to the backup firmware bank and gives you
the opportunity to recover the firmware in the primary bank. For instructions for recovering the UEFI
firmware, see “Recovering the server firmware (UEFI update failure)” on page 76. After you have recovered
the firmware in the primary bank, do the following:
Step 1. Restart the server.

Step 2. When the prompt Press F3 to restore to primary is displayed, press F3 to start the server from the
primary bank.
Nx-boot failure
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:
• The server restarts automatically and attempts POST again.
• 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 complete POST
with the default configuration successfully, there might be a problem with the system board.
You can set the number of consecutive restart attempts that will trigger the Nx-boot failure feature, in the
Setup Utility. To specify the number, click System Settings ➙ Recovery ➙ POST Attempts ➙ POST
Attempts Limit. Then, choose the item from the following available options: 3, 6, 9, and Disable Nx-boot
failure.

Chapter 6. Parts listing, Lenovo System x3250 M6
The following replaceable components are available for the Lenovo System x3250 M6 server, except as
specified otherwise in “Replaceable server components” on page 79. For an updated parts listing, go to
http://www.lenovo.com/support.
Replaceable server components

This topic describes the replaceable server components for Lenovo System x3250 M6.
Replaceable components consist of structural parts, and field replaceable units (FRUs):
• Structural parts: Purchase and replacement of structural parts (components, such as chassis assembly,
cover, and bezel) is your responsibility. If Lenovo acquires or installs a structural component at your
request, you will be charged for the service. For the list of structural parts, see “Structural parts” on page
90.
• Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your responsibility. If Lenovo
installs a Tier 1 CRU at your request, you will be charged for the installation.
• Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or request Lenovo to install it, at
no additional charge, under the type of warranty service that is designated for your server.
For information about the terms of the warranty and getting service and assistance, see the Warranty
Information document that comes with the server. For more information about getting service and
assistance, see Appendix D “Getting help and technical assistance” on page 589.
Visit http://www.lenovo.com/ serverproven/ for the latest options supporting plan.
The following illustration shows the major components in the server. The illustrations in this document might
differ slightly from your hardware. For a list of structural parts, see “Structural parts” on page 90.

The following table lists the part numbers for the server replaceable components.
CRU part
number (Tier CRU part
Index Description 1) number (Tier 2)
3 Heat sink 00YJ784

4 Memory, 4 GB dual-rank 1.2 V, DDR4, 2133 MHz, ECC UDIMM 46W0811
4 Memory, 8 GB single-rank 1.2 V, DDR4, 2400 MHz, ECC UDIMM 01KN323

(Kabylake)
4 Memory, 8 GB single-rank 1.2 V, DDR4, 2400 MHz, ECC UDIMM 01KN344
4 Memory, 16 GB dual-rank 1.2 V, DDR4, 2400 MHz, ECC UDIMM 01KN346
4 Memory, 16 GB dual-rank 1.2 V, DDR4, 2400 MHz, ECC UDIMM 01KN327

(Kabylake)

CRU part
5 Fixed power supply, 300 watts 00YD993
6 Hot-swap power supply, 460 watts 69Y5939
6 AcBel power supply, 460 watts 00YJ944
6 AcBel power supply, 460 watts 00MX952
9 Power distribution board 00YJ453

10 Backplate assembly, four 2.5-inch simple-swap hard disk drives, 00YE174
software RAID
hardware RAID
10 Backplate assembly, eight 2.5-inch simple-swap hard disk drives, 00YE173
hardware RAID
software RAID
hardware RAID
12 Backplane, four 2.5-inch hot-swap hard disk drives 00FJ755
13 Backplane, four 3.5-inch hot-swap hard disk drives 00FJ752
16 Ultra-Slim SATA DVD-ROM, 9.5 mm 00FL352

16 Ultra-Slim SATA Multi-Burner, 9.5 mm 00FL353
18 Hard disk drive, 3.5-inch hot-swap, SATA, 500 GB, 7.2 K 81Y9787
18 Hard disk drive, 3.5-inch hot-swap, SATA, 2 TB, 7.2 K 00FN114
18 Hard disk drive, 3.5-inch hot-swap, SATA, 8 TB, 7.2 K 00WH127
18 Hard disk drive, 3.5-inch hot-swap, SAS, 2 TB, 7.2 K 00FN189
18 Hard disk drive, 3.5-inch hot-swap, SAS, 2 TB, 7.2 K 00YK001
18 Hard disk drive, 3.5-inch hot-swap, SAS, 8 TB, 7.2 K 00WH122
18 Hard disk drive, 3.5-inch hot-swap, SAS, 300 GB, 15 K 00WG676
18 Hard disk drive, 3.5-inch hot-swap, SATA, 1 TB, 7.2 K 81Y9791
18 Solid-state drive, 3.5-inch hot-swap, SATA, 480 GB 00YK238
Chapter 6. Parts listing, Lenovo System x3250 M6 81

CRU part
18 Solid-state drive, 3.5-inch hot-swap, SATA, 1.2 GB 00YK248
18 Solid-state drive, 3.5-inch hot-swap, SATA, 1.6 GB 00YK253
18 Solid-state drive, 3.5-inch hot-swap, SATA, 240 GB 01GV869
18 Solid-state drive, 3.5-inch hot-swap, SATA, 1.92 TB 01GV884
18 Solid-state drive, 3.5-inch hot-swap, SATA, 480 GB 01KR517
18 Solid-state drive, 3.5-inch hot-swap, SATA, 1.92 TB 01KR527
19 Hard disk drive, 3.5-inch simple-swap, SATA, 500 GB, 7.2 K 81Y9803
19 Hard disk drive, 3.5-inch simple-swap, SATA, 2 TB, 7.2 K 00FN119
19 Hard disk drive, 3.5-inch simple-swap, SATA, 4 TB, 7.2 K 00FN149
19 Hard disk drive, 3.5-inch simple-swap, SATA, 10 TB, 7.2 K 00YK342
19 Hard disk drive, 3.5-inch simple-swap, SATA, 1 TB, 7.2 K 81Y9807
19 Hard disk drive, 3.5-inch hot-swap, SAS, 12 TB, 7.2 K 01GV056
19 Hard disk drive, 3.5-inch hot-swap, SATA, 12 TB, 7.2 K 01GV061
19 Solid-state drive, 3.5-inch hot-swap, SATA, 1.2 TB, S3520 01GR808
19 Solid-state drive, 3.5-inch hot-swap, SATA, 800 GB, S3520 01KR472
19 Solid-state drive, 3.5-inch hot-swap, SATA, 240 GB 01GR900
19 Solid-state drive, 3.5-inch hot-swap, SAS, 3.84 TB 01GR792
19 Solid-state drive, 3.5-inch hot-swap, SATA, 240 GB 01GT771

CRU part
20 Hard disk drive, 2.5-inch hot-swap, SAS, 900 GB 01GV041
20 Hard disk drive, 2.5-inch hot-swap, SAS, 2.4 TB, 10 K 01GV071
20 Hard disk drive, 2.5-inch hot-swap, SATA, 1 TB, 7.2 K 00AJ142
20 Hard disk drive, 2.5-inch hot-swap, SATA, 2 TB, 7.2 K 00NA527
20 Hard disk drive, 2.5-inch hot-swap, SAS, 1 TB, 7.2 K 00NA492
20 Hard disk drive, 2.5-inch hot-swap, SAS, 2 TB, 7.2 K 00NA497
20 Hard disk drive, 2.5-inch hot-swap, SAS, 900 GB, 15 K 01GV036
20 Hard disk drive, 2.5-inch hot-swap, SAS, 1.2 TB, 10 K 00WG701
20 Hard disk drive, 2.5-inch hot-swap, SAS, 1.8 TB, 10 K 00NA272
20 Solid-state drive, 2.5-inch hot-swap, SATA, 120 GB 00WG621
20 Solid-state drive, 2.5-inch hot-swap, SATA, 200 GB 00YC321
20 Solid-state drive, 2.5-inch hot-swap, SAS, 3.84 TB 01GR787
20 Solid-state drive, 2.5-inch hot-swap, SATA, 1.2 TB, S3520 series 01GR803

CRU part
20 Solid-state drive, 2.5-inch hot-swap, SATA, 800 GB, S3520 01KR467
20 Solid-state drive, 2.5-inch hot-swap, SAS, 1.2 TB, 10 K 00WG721
21 Hard disk drive, 2.5-inch simple-swap, SATA, 1.2 TB 00YK223
21 Hard disk drive, 2.5-inch simple-swap, SATA, 1.6 TB 00YK228
21 Hard disk drive, 2.5-inch simple-swap, SATA, 1 TB, 7.2 K 00NA627
21 Hard disk drive, 2.5-inch simple-swap, SATA, 2 TB, 7.2 K 00NA537
23 Hard disk drive filler, one 2.5-inch hard disk drive 00FW856
24 Front I/O assembly 00AL324
25 System board (Skylake) 00YJ451
25 System board (Kabylake) 01GT311
27 System fan 00YJ785
28 Microprocessor, Intel Pentium G4620, 3.7 GHz, 2400 MHz, 51 W (2- 01GT303
core, Kabylake)
28 Microprocessor, Intel Pentium G4520, 3.6 GHz, 3 MB, 2133 MHz, 65 00YE094
W (2-core)
core, Kabylake)

CRU part
W (2-core)
28 Microprocessor, Intel Pentium G4600T, 3.0 GHz, 2400 MHz, 35 W (2- 01GT305
core, Kabylake)
28 Microprocessor, Intel Pentium G4500T, 3.0 GHz, 3 MB, 2133 MHz, 35 00YE096
W (2-core)
core, Kabylake)
W (2-core)
28 Microprocessor, Intel Pentium G4560T, 2.9 GHz, 2400 MHz, 35 W (2- 01GT307
core, Kabylake)
28 Microprocessor, Intel Pentium G4400T, 2.9 GHz, 3 MB, 2133 MHz, 35 00YE098
W (2-core)
28 Microprocessor, Intel Core-i3 7320, 4.1 GHz, 2400 MHz, 51W (2-core, 01GT298
Kabylake)
28 Microprocessor, Intel Core-i3 7300, 4.0 GHz, 2400 MHz, 51 W (2-core, 01GT299
Kabylake)
28 Microprocessor, Intel Core-i3 6320, 3.9 GHz, 4 MB, 2133 MHz, 65 W 00YE089
(2-core)
(2-core)
28 Microprocessor, Intel Core-i3 7300T, 3.5 GHz, 2400 MHz, 35 W (2- 01GT300
core, Kabylake)
28 Microprocessor, Intel Core-i3 6300T, 3.3 GHz, 4 MB, 2133 MHz, 35 W 00YE091
(2-core)
28 Microprocessor, Intel Core-i3 7100, 3.9 GHz, 2400 MHz, 51 W (2-core, 01GT301
Kabylake)
(2-core)
28 Microprocessor, Intel Core-i3 7100T, 3.4 GHz, 2400 MHz, 35 W (2- 01GT302
core, Kabylake)
28 Microprocessor, Intel Core-i3 6100T, 3.2 GHz, 3 MB, 2133 MHz, 35 W 00YE093
(2-core)
28 Microprocessor, Intel Xeon E3-1280 v6, 3.9 GHz, 2400 MHz, 72 W (4- 01GT292
core,Kabylake)
28 Microprocessor, Intel Xeon E3-1280 v5, 3.7 GHz, 8 MB cache, 2133 00YE086
MHz, 80 W (4-core)
core, Kabylake)
MHz, 80 W (4-core)

CRU part
28 Microprocessor, Intel Xeon E3-1260L v5, 2.9 GHz, 8 MB cache, 2133 00YE087
MHz, 45 W (4-core)
28 Microprocessor, Intel Xeon E3-1240L v5, 2.1 GHz, 8 MB cache, 2133 00YE088
MHz, 25 W (4-core)
core, Kabylake)
MHz, 80 W (4-core)
core, Kabylake)
MHz, 80 W (4-core)
core, Kabylake)
core, Kabylake)
MHz, 80 W (4-core)
28 Microprocessor, Intel Celeron G3950, 3.0 GHz, 2400 MHz, 51 W (2- 01GT308
core, Kabylake)
28 Microprocessor, Intel Celeron G3930, 2.9 GHz, 2400 MHz, 51 W (2- 01GT309
core, Kabylake)
28 Microprocessor, Intel Celeron G3920, 2.9 GHz, 2 MB, 2133 MHz, 65 W 00YE099
(2-core)
28 Microprocessor, Intel Celeron G3900, 2.8 GHz, 2 MB, 2133 MHz, 65 W 00YE100
(2-core)
28 Microprocessor, Intel Celeron G3930T, 2.7 GHz, 2400 MHz, 35 W (2- 01GT310
core, Kabylake)
28 Microprocessor, Intel Celeron G3900T, 2.6 GHz, 2 MB, 2133 MHz, 35 00YE101
W (2-core)
30 ServeRAID M1210 SAS/SATA Controller 00JY196

30 ServeRAID M1215 SAS/SATA Controller 46C9115
30 ServeRAID M5225 SAS/SATA Controller 00AE939
30 ServeRAID M5210 SAS/SATA Controller 46C9111
30 ServeRAID M5200 Series 1GB Cache (RAID 5 Upgrade) 47C8657
30 ServeRAID M5200 Series 1GB Flash (RAID 5 Upgrade) 47C8661
30 N2215 SAS/SATA HBA 47C8676

30 N2225 SAS/SATA HBA 00AE914

CRU part
30 QLogic 8 Gb FC Single-port HBA 00Y5628
30 QLogic 8 Gb FC Dual-port HBA 00Y5629
30 Emulex 8 Gb FC Single-port HBA 42D0491
30 Emulex 8 Gb FC Dual-port HBA 00JY848
30 Intel X710 2x10GbE SFP+ Adapter 81Y3522
30 Intel X710-DA2 2x10GbE SFP+ Adapter 01DA902
30 Broadcom NetXtreme I Dual Port GbE Adapter 90Y9373
30 Intel I350-T2 2xGbE BaseT Adapter 00AG512
30 Intel I350-T4 4xGbE BaseT Adapter 00AG522
30 Intel X710-T4 4x10 Gb BaseT Adapter 01GR282
30 Emulex VFA5.2 2x10 GbE SFP+ PCIe Adapter 01KR603
30 Emulex VFA5.2 2x10 GbE SFP+ PCIe Adapter 00AG573
30 Intel X550-T2 Dual Port 10GBase-T Adapter 00MM862
Operating temperature enhancement kit 46W9221
Battery, 3.0 volts 33F8354
Label, chassis 00YE179

Serial Port Upgrade Kit 00KC965
PCI riser card 00YJ452

Silicom x540 NIC Card 01PG489
Optical Blank Filler 00KF416
Four 2.5–inch BP Bracket 00KF692

4G USB Memory Key 00WH143
2.8 m, 10A/250 V, C13 to IRAM 2073 (Argentina) Line Cord 39M5068
4.3 m, 10A/125 V, C13 to NEMA 5-15P (US) Line Cord 39M5076
2.8 m, 10A/250 V, C13 to AS/NZ 3112 (Australia/NZ) Line Cord 39M5102
2.8 m, 10A/230 V, C13 to CEE7-VII (Europe) Line Cord 39M5123
2.8 m, 10A/250 V, C13 to DK2-5a (Denmark) Line Cord 39M5130
2.8 m, 10A/250 V, C13 to SABS 164 (S Africa) Line Cord 39M5144
2.8 m, 10A/250 V, C13 to BS 1363/A (UK) Line Cord 39M5151
2.8 m, 10A/250 V, C13 to SEV 1011-S24507 (Swiss) Line Cord 39M5158
2.8 m, 220-240 V, C13 to CEI 23-16 (Italy/Chile) Line Cord 39M5165
2.8 m, 10A/250 V, C13 to SI 32 (Israel) Line Cord 39M5172
2.8 m, 12A/125 V, C13 to JIS C-8303 (Japan) Line Cord 39M5199
4.3 m, 12A/100 V, C13 to JIS C-8303 (Japan) Line Cord 39M5200

CRU part
2.8 m, 220-240 V, C13 to GB 2099.1 (China) Line Cord 39M5206
2.8 m, 220-240 V, C13 to KETI (S Korea) Line Cord 39M5219
2.8 m, 250 V, C13 to NBR 14136 (Brazil) Line Cord 39M5240
2.8 m, 10 A/240 V, C13 to CNS 10917-3 (Taiwan) Line Cord 39M5254
1.5 m, 10 A/100-250 V, C13 to IEC 320-C14 Rack Power Cable 39M5375

2.8 m, 10 A/125 V, C13 to CNS 10917 (Taiwan) Line Cord 39M5463
QLogic 10 Gb SFP+ SR Optical Transceiver 42C1816
SFP+ SR Transceiver 46C3449

Brocade 10 Gb SFP+ SR Optical Transceiver 46C9297
425 mm & 925 mm ServeRAID M5200 Series Flash Power Module 46C9793
Cable
ServeRAID M5200 Series 1 GB Cache/RAID 5 Upgrade 44W3392
ServeRAID M5200 Series 1 GB Flash/RAID 5 Upgrade 44W3393
RDX 3.0 external tape drive 00MW718
Keyboard, professional, US English 103P RoHS v2 00AL883
Keyboard, pointing device, US English 103P RoHS v2 00MW364
Mouse, two button optical wheel 00MW370
RDX 3.0 External TD 00MW718

Cable, 3 meters external USB 3.0 00MW395
Cable, Mini-SAS, four 3.5-inch hard-disk-drive backplate, software 00YJ410

RAID
Cable, Mini-SAS, four 2.5-inch hard-disk-drive backplate, software 00YJ411
RAID
Cable, Mini-SAS, four 3.5-inch hard-disk-drive backplate, hardware 00YJ412
RAID
Cable, Mini-SAS, the first four 2.5-inch hard-disk-drive backplate, 00YJ413
hardware RAID
Cable, Mini-SAS, the second four 2.5-inch hard-disk-drive backplate, 00YJ414
hardware RAID
Cable, Mini-SAS, four 3.5-inch or the first four 2.5-inch hard-disk-drive 00YJ415
backplane
Cable, Mini-SAS, the second four 2.5-inch hard-disk-drive backplane 00YJ416
Power cable, backplane, four 2.5-inch hot-swap hard disk drive 00YJ417

CRU part
Power cable, backplane, four 3.5-inch hot-swap hard disk drive 00YJ418
Power cable, system board 00YJ419
Power cable, microprocessor 00YJ420
Signal cable, power distribution board to system board 00YJ421
Cable, SATA Slimline 81Y6774

Cable, Mini-SAS 1 m, 6 Gbps, SFF-8644 to SFF-8088 00YE304
ServeRAID M5100/M5200 Series flash power module 00JY023
Cable, configuration (eight HDDs)
Cable, power (for four hot-swap HDDs)
Cable, SATA slimline

Cable, SAS signal (840 mm)
Consumable parts (parts that are purchased separately) are not covered by the Lenovo Statement of Limited
Warranty. The following consumable parts are available for purchase from the retail store.
Index Description Part number
1 Server cover, for server models with hot swap power supply 00YE167
1 Server cover, for server models with fixed power supply 00YE168
2 Air baffle 00AL326

7 Chassis assembly, 3.5-inch HDD (hot-swap power supply model) 00YE164
15 Chassis assembly, 2.5-inch HDD (fixed power supply model) 00YE165
Chassis assembly, 2.5-inch HDD (hot-swap power supply model) 00YE166
Chassis assembly, 3.5-inch HDD (fixed power supply model) 00YE163
8 Power distribution board cover 00YE169

17 Hard disk drive filler, 3.5-inch hot-swap 69Y5364
17 Hard disk drive filler, 3.5-inch simple-swap 69Y5368
26 RAID adapter battery or flash power module holder 00Y8545
Optical drive filler 00YE175
Rack release latch (Left) 00YE176
Rack release latch (Right) 00YE177
PCI riser-card cage 00YE192
Label, system service, FRU/CRU 00YE353

Rail kit 00MV390

Power-supply filler 49Y4821
Structural parts
Structural parts are not covered by the Lenovo Statement of Limited Warranty. You can place an order on the
structural parts from the Lenovo retail store.
The following structural parts are available for purchase from the retail store.
Table 25. Structural parts, Type 3633 and 3943

14 Security bezel 00KF695
22 2.5-inch hard disk drive filler (for two hard disk drives) 00KF683
To order a structural part, do the following:
Note: Changes are made periodically to the Lenovo Web site. The actual procedure might vary slightly from
what is described in this document.
1. Go to http://www.ibm.com.
2. From the Products menu, select Upgrades, accessories & parts.
3. Click Obtain maintenance parts; then, follow the instructions to order the part from the retail store.
If you need help with your order, call the toll-free number that is listed on the retail parts page, or contact
your local Lenovo representative for assistance.
Power cords
For your safety, a power cord with a grounded attachment plug is provided to use with this product. To avoid
electrical shock, always use the power cord and plug with a properly grounded outlet.
Lenovo power cords used in the United States and Canada are listed by Underwriter's Laboratories (UL) and
certified by the Canadian Standards Association (CSA).
For units intended to be operated at 115 volts: Use a UL-listed and CSA-certified cord set consisting of a
minimum 18 AWG, Type SVT or SJT, three-conductor cord, a maximum of 15 feet in length and a parallel
blade, grounding-type attachment plug rated 15 amperes, 125 volts.
For units intended to be operated at 230 volts (U.S. use): Use a UL-listed and CSA-certified cord set
consisting of a minimum 18 AWG, Type SVT or SJT, three-conductor cord, a maximum of 15 feet in length
and a tandem blade, grounding-type attachment plug rated 15 amperes, 250 volts.
For units intended to be operated at 230 volts (outside the U.S.): Use a cord set with a grounding-type
attachment plug. The cord set should have the appropriate safety approvals for the country in which the
equipment will be installed.
Power cords for a specific country or region are usually available only in that country or region.

Power cord part number Used in these countries and regions
39M5206 China
39M5102 Australia, Fiji, Kiribati, Nauru, New Zealand, Papua New Guinea
39M5123 Afghanistan, Albania, Algeria, Andorra, Angola, Armenia, Austria, Azerbaijan, Belarus,
Belgium, Benin, Bosnia and Herzegovina, Bulgaria, Burkina Faso, Burundi,
Cambodia, Cameroon, Cape Verde, Central African Republic, Chad, Comoros, Congo
(Democratic Republic of), Congo (Republic of), Cote D’Ivoire (Ivory Coast), Croatia
(Republic of), Czech Republic, Dahomey, Djibouti, Egypt, Equatorial Guinea, Eritrea,
Estonia, Ethiopia, Finland, France, French Guyana, French Polynesia, Germany,
Greece, Guadeloupe, Guinea, Guinea Bissau, Hungary, Iceland, Indonesia, Iran,
Kazakhstan, Kyrgyzstan, Laos (People’s Democratic Republic of), Latvia, Lebanon,
Lithuania, Luxembourg, Macedonia (former Yugoslav Republic of), Madagascar, Mali,
Martinique, Mauritania, Mauritius, Mayotte, Moldova (Republic of), Monaco,
Mongolia, Morocco, Mozambique, Netherlands, New Caledonia, Niger, Norway,
Poland, Portugal, Reunion, Romania, Russian Federation, Rwanda, Sao Tome and
Principe, Saudi Arabia, Senegal, Serbia, Slovakia, Slovenia (Republic of), Somalia,
Spain, Suriname, Sweden, Syrian Arab Republic, Tajikistan, Tahiti, Togo, Tunisia,
Turkey, Turkmenistan, Ukraine, Upper Volta, Uzbekistan, Vanuatu, Vietnam, Wallis
and Futuna, Yugoslavia (Federal Republic of), Zaire
39M5130 Denmark
39M5179
39M5144 Bangladesh, Lesotho, Macao, Maldives, Namibia, Nepal, Pakistan, Samoa, South
Africa, Sri Lanka, Swaziland, Uganda
39M5151 Abu Dhabi, Bahrain, Botswana, Brunei Darussalam, Channel Islands, China (Hong
Kong S.A.R.), Cyprus, Dominica, Gambia, Ghana, Grenada, Iraq, Ireland, Jordan,
Kenya, Kuwait, Liberia, Malawi, Malaysia, Malta, Myanmar (Burma), Nigeria, Oman,
Polynesia, Qatar, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the
Grenadines, Seychelles, Sierra Leone, Singapore, Sudan, Tanzania (United Republic
of), Trinidad and Tobago, United Arab Emirates (Dubai), United Kingdom, Yemen,
Zambia, Zimbabwe
39M5158 Liechtenstein, Switzerland
39M5165 Chile, Italy, Libyan Arab Jamahiriya
39M5172 Israel
39M5095 220 - 240 V
Antigua and Barbuda, Aruba, Bahamas, Barbados, Belize, Bermuda, Bolivia, Caicos
Islands, Canada, Cayman Islands, Colombia, Costa Rica, Cuba, Dominican Republic,
Ecuador, El Salvador, Guam, Guatemala, Haiti, Honduras, Jamaica, Mexico,
Micronesia (Federal States of), Netherlands Antilles, Nicaragua, Panama, Peru,
Philippines, Saudi Arabia, Thailand, Taiwan, United States of America, Venezuela
39M5076 110 - 120 V

39M5081
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
39M5463 Taiwan
39M5087 Thailand
39M5219 Korea (Democratic People’s Republic of), Korea (Republic of)
39M5199 Japan

Power cord part number Used in these countries and regions
39M5068 Argentina, Paraguay, Uruguay
39M5226 India
39M5240 Brazil
39M5241
39M5375 Canada, United States of America
39M5377
39M5378
39M5509
39M5512

Chapter 7. Removing and installing server components
This chapter provides instructions on how to remove and install hardware for your server. You can expand
the capabilities of your server by adding new hardware devices, such as memory modules, PCIe cards, or
other server options, and maintain your server by replacing the failing hardware devices. If you are handling a
server option, refer to the appropriate installation and or removal instructions in this topic along with the
instructions that come with the option.
For information about warranty terms, see the Warranty Information document that comes with the server.
For more information about getting service and assistance, see Appendix D “Getting help and technical
assistance” on page 589.
Before removing or installing server components

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 device.
System reliability guidelines

To help ensure proper system cooling and system reliability, make sure that the following requirements are
met:
• Each of the drive bays has a drive in it, otherwise a filler and electromagnetic compatibility (EMC) shield
installed must be installed.
• If the server has redundant power, each of the power-supply bays has a power supply installed.
• There is adequate space around the server to ensure the server cooling system works properly. Leave
approximately 50 mm (2.0 inches) of open space around the front and rear of the server. Do not place
objects in front of the fans. For proper cooling and airflow, install the server cover before you turn on the
server. Operating the server for extended periods of time (more than 30 minutes) with the server cover
removed might damage server components.
• You have followed the cabling instructions that come with optional adapters.
• You have replaced a failed fan as soon as possible.
• You have replaced a hot-swap drive within two minutes of removal.
• You operate the server with the air baffle installed. Operating the server without the air baffle might cause
the microprocessor to overheat.
Working inside the server with the power on

Guidelines to work inside the server with the power on.
Attention: Static electricity that is released to internal server components when the server is powered-on
might cause the server to halt, which might result in the loss of data. To avoid this potential problem, always
use an electrostatic-discharge wrist strap or other grounding system when you work inside the server with
the power on.
You might have to have the server turned on while the cover is off, to look at system-board LEDs or replace
hot-swap components. Follow these guidelines when you work inside a server that is turned on:
• Avoid wearing loose-fitting clothing on your forearms. Button long-sleeved shirts before working inside
the server; do not wear cuff links while you are working inside the server.

• Do not allow your necktie or scarf to hang inside the server.
• Remove jewelry, such as bracelets, necklaces, rings, and loose-fitting wrist watches.
• Remove items from your shirt pocket, such as pens and pencils, that could fall into the server as you lean
over it.
• Avoid dropping any metallic objects, such as paper clips, hairpins, and screws, into the server.
Handling static-sensitive devices

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

This section provides information for removing and installing server components.
Removing and installing structural parts

Installation of structural parts is your responsibility. If Lenovo installs a structural part at your request, you will
be charged.
Removing the server cover

To remove the server cover, do the following:
Step 1. Turn off the server. Then, disconnect all external cables and remove all peripheral devices.
Step 2. If the server has been installed in a rack, remove the server from the rack. See the Rack Installation
Instructions that comes with the server.
Step 3. Put the server on a working area before you remove any server components from the server.
Step 4. Put your thumbs on the blue cover-release buttons 1 and 2. Firmly press the button 1 and slide the
server cover toward the rear of the server until the cover is disengaged from the chassis.

Figure 15. Server cover removal
Step 5. Lift the server cover off the server and set it aside.
Attention: For proper cooling and airflow, install the server cover before you turn on the server.
Installing the server cover

To install the server cover, do the following:
Note: Ensure that all components have been reassembled properly and that no tools or loose screws are left
inside your server.
Step 1. Position the server cover on top of the server.

Step 2. Slide the server cover toward the front of the server. Make sure that the server cover properly
engages all the inset tabs on the server.
Figure 16. Server cover installation
Step 3. Install the server into the rack. See the Rack Installation Instructions that comes with the server.
Step 4. Reconnect all the external cables. Then, turn on the server and peripheral devices.
Removing the air baffle

To remove the air baffle, do the following:
Chapter 7. Removing and installing server components 95

Step 3. Hold the air baffle and lift it out of the server.
Figure 17. Air baffle removal
Attention: For proper cooling and airflow, install the air baffle before you turn on the server.
Operating the server with the air baffle removed might damage server components.
Installing the air baffle

If you have removed the air baffle, you need to reinstall the air baffle or install a new one if the old one is
broken.
To install the air baffle, do the following:
Step 1. Align the air baffle tabs 1 with the notches in the server fan cage. Then, lower the air baffle into the
server and press the air baffle down until it is securely seated.
Figure 18. Air baffle installation

Step 2. Complete the parts replacement. See “Completing the parts replacement” on page 170.
Removing the security bezel

To remove the security bezel, do the following:

Step 2. Use the key to unlock the security bezel to the open position.
Figure 19. Unlocking the security bezel
Step 3. Press the release latch 1 and pivot the security bezel outward to remove it from the chassis.
Figure 20. Security bezel removal
Installing the security bezel

To install the security bezel, do the following:

Step 2. Carefully insert the tab on the security bezel into the slot on the right side of the chassis. Then,
press and hold the release latch and pivot the security bezel inward until the other side clicks into
place.

Figure 21. Security bezel installation
Step 3. Use the key to lock the security bezel to the closed position.
Figure 22. Locking the security bezel
Removing the PCI riser-card assembly

To remove the PCI riser-card assembly, do the following:
Step 3. Grasp the blue tabs on the PCI riser-card assembly and lift the PCI riser-card assembly to release it
from the chassis.

Figure 23. PCI riser-card assembly removal
Step 4. Disconnect any cables from the adapters on the PCI riser-card assembly.
Step 5. Remove the adapter from the PCI riser-card assembly. See “Removing an adapter” on page 114.
Step 6. Place the PCI riser-card assembly on a flat, static-protective surface.
Step 7. Install the PCI riser-card assembly. See “Installing the PCI riser-card assembly” on page 99.
Installing the PCI riser-card assembly

If you have removed the PCI riser-card assembly, you need to install it the before turning on the server. To
install the PCI riser-card assembly, do the following:
Step 1. Install the appropriate adapters onto the PCI riser-card assembly. See “Installing an adapter” on
page 114.
Step 2. Reconnect any adapter cables that you disconnected when you removed the PCI riser-card
assembly.
Step 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 fingers on 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.

Figure 24. PCI riser-card assembly installation
Removing the flash power module holder

Note: The flash power module holder is supported on the 2.5-inch-drive server models only.
To remove the flash power module holder, do the following:
Step 3. Remove the flash power module. See “Removing a RAID adapter battery or flash power module”
on page 118.
Step 4. Remove the two screws that secure the holder and then remove the holder.
Figure 25. Flash power module holder removal

Installing flash power module holder

Note: The RAID adapter battery or flash power module holder is supported on the 2.5-inch-drive server
models only.
To install flash power module holder, do the following:
Step 3. Place the holder on the chassis as shown and align the screw holes in the holder with the ones in
the chassis. Then, install the two screws and make sure that the holder is secured firmly on the
chassis.
Figure 26. Flash power module holder installation
Step 4. Install a flash power module. See “Installing a RAID adapter battery or flash power module” on
page 118.
Removing and installing Tier 1 CRUs

Installation of Tier 1 CRUs is your responsibility. If Lenovo installs a Tier 1 CRU at your request, you will be
charged.
Removing a DIMM
To remove a DIMM, do the following:
Step 3. Remove the air baffle. See “Removing the air baffle” on page 95.
Step 4. Carefully open the retaining clips 1 on each end of the DIMM slot and remove the DIMM.

Attention: To avoid breaking the retaining clips or damaging the DIMM slots, handle the clips
gently.
Figure 27. DIMM removal
Step 5. Install a new DIMM if you have installed only one DIMM. See “Installing a DIMM” on page 104.
DIMM installation guidelines

The following tips describe the types of DIMMs that the server supports and other information that you must
consider when you install DIMMs.
• Confirm that the server supports the DIMM that you are installing. Go to:
• When you install or remove DIMMs, the server configuration information changes. When you restart the
server, the system displays a message indicating that the memory configuration has been changed. You
can use the Setup Utility program to view the server configuration information. See “Using the Setup
Utility program” on page 29.
• The server supports only industry-standard DDR4, 2133 MHz, PC4-17000 (single-rank or dual-rank),
unbuffered DIMMs with error correcting code (ECC).
• The server supports a maximum of four single-rank or dual-rank unbuffered DIMMs.
• The maximum operating speed of the server is determined by the slowest DIMM in the server.
• If you install a pair of DIMMs in DIMM slots 3 and 1, the size and speed of the DIMMs that you install in
DIMM slots 1 and 3 must match each other. However, they do not have to be the same size and speed as
the DIMMs that are installed in DIMM slots 4 and 2.
• You can use compatible DIMMs from various manufacturers in the same pair.
• To determine the type of a DIMM, see the label on the DIMM. The information on the label is in the format
x GB nRxx PC4-xxxxxx-xx-xx-xx. The “nRxx” indicates whether the DIMM is single-rank (n=1) or dual-
rank (n=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 Setup Utility. For additional information, see “Configuring the server”
on page 26.
• The specifications of a DDR4 DIMM are on a label on the DIMM, in the following format:

gggGBpheRxff PC4-wwwwaa-mccd-bb
where:
– gggGB is the total capacity of the DIMM (for example, 1 GB, 2 GB, or 4 GB)
– pheR is the number of package ranks and number of logical ranks per package rank
p has the following variables:
– 1 = 1 package rank of SDRAMs installed
– 2 = 2 package ranks of SDRAMs installed
– he: blank for monolithic DRAMs and others for modules using stacked DRAM.
h is the DRAM package type. It has the following variables:
– D = multi-load DRAM stacking (DDP)
– Q = multi-load DRAM stacking (QDP)
– D = single load DRAM stacking (3DS)
e: blank for SDP, DDP and QDP and others for modules using 3DS stacks, logical ranks per package
rank
It has the following variables:
– 2 = 2 logical ranks in each package rank
– xff is the device organization or bit width of SDRAMs (for example, x4, x8, or x16)
– x4 = x4 organization (four DQ lines per SDRAM)
– x8 = x8 organization
– x16 = x16 organization
– wwww is the DIMM speed, in MBps (for example, 2133, 2400, 2666, 2933, or 3200)
aa is the SDRAM speed grade
– m is the DIMM type
– E = Unbuffered DIMM (UDIMM) (x64-bit primary data bus) with ECC (x8-bit module data bus)
– L = Load Reduced DIMM (LRDIMM) (x64-bit primary data bus) with ECC (x8-bit module data bus)
– R = Registered DIMM (RDIMM) (x64-bit primary data bus) with ECC (x8-bit module data bus)
– U = Unbuffered DIMM with no ECC (x64-bit primary data bus)
cc is the reference design file for the design of the DIMM
d is the revision number of the used reference design
– bb is the JEDEC SPD Revision Encoding and Additions level
To locate the DIMM slots on the system board, see “System-board connectors” on page 21.
The following sections provide additional information specific to unbuffered DIMMs that you must consider.
Unbuffered DIMMs (UDIMMs)

The following tips provide information that you must consider when you install UDIMMs.
• The memory channels run at the lowest common frequency of the DIMMs installed.

• The UDIMM options that are available for the server are 4 GB, 8 GB, and 16 GB DIMMs.
• The server supports up to two single-rank or dual-rank UDIMMs per channel.
• It is recommended to install DIMMs with the same rank in each channel.
• The following table lists the supported UDIMM population.
Table 26. Supported UDIMM population per channel
DIMM slots per DIMMs installed in Ranks per DIMM

channel each channel DIMM type DIMM speed (any combination)
2 1 Unbuffered DDR4 2133/2400 Dual-rank

ECC
2 2 Unbuffered DDR4 2133/2400 Dual-rank
ECC
• The following table lists the maximum DIMM population using ranked UDIMMs.
Table 27. Maximum memory population using ranked UDIMMs (depending on your model)
Number of UDIMMs DIMM type Size Total memory
4 Dual-rank UDIMMs 16 GB 64 GB
• The following table shows the UDIMM memory installation sequence to optimize the system performance.
Table 28. DIMM installation sequence
Number of DIMMs Installation sequence (DIMM slots)
First pair of DIMMs 3, 1
Second pair of DIMMs 4, 2
Installing a DIMM
To install a DIMM, do the following:
Step 4. Locate the DIMM slots on the system board. Then, refer to “Unbuffered DIMMs (UDIMMs)” on page
103 and ensure that you observe the installation rules and sequence.
Step 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.
Step 6. Open the retaining clips 1 on each end of the DIMM slot. Then, install the DIMM into the slot.
Attention: To avoid breaking the retaining clips or damaging the DIMM slots, open and close the
clips gently.

Figure 28. DIMM installation
Step 7. 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.
Removing a hot-swap hard disk drive

The drive ID that is assigned to each drive is printed on the front of the server. The ID numbers and the drive
bay numbers are the same. For detailed information, see “Front view” on page 15.
Attention:
• To avoid damage to the hard disk drive connectors, make sure that the server cover is in place and fully
closed whenever you install or remove a hard disk drive.
• To ensure adequate system cooling, do not operate the server for more than two minutes without either a
hard disk drive or a filler installed in each bay.
• Before you change hard disk drives, HDD controllers (including controllers that are integrated on the
system board), HDD backplanes, or HDD cables, back up all important data that is stored on the hard disk
drives.
• Before you remove any component of a RAID array, back up all RAID configuration information and data
on your drive.
To remove a hot-swap hard disk drive, do the following:
Step 1. Remove the security bezel. See “Removing the security bezel” on page 97.
Step 2. Press the release button 1 to open the handle 2 of the drive. Then, grasp the handle and pull the
hot-swap hard disk drive out of the drive bay.

Figure 29. 2.5-inch hot-swap hard disk drive removal
Figure 30. 3.5-inch hot-swap hard disk drive removal
Step 3. Install a new hot-swap hard disk drive or install a filler into the bay.
Step 4. Reinstall the security bezel. See “Installing the security bezel” on page 97.
Installing a hot-swap hard disk drive

Attention: To avoid damage to the hard disk drive connectors, make sure that the server cover is in place
and fully closed whenever you install or remove a hard disk drive.
The following tips 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.
• Locate the documentation that comes with the hard disk drive and follow those instructions in addition to
the instructions in this topic.
• Make sure that you have all the cables and other equipment specified in the documentation that comes
with the drive.
• Select the bay in which you want to install the drive.
• 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.
• You can install up to eight 2.5-inch or four 3.5-inch hot-swap SAS or SATA hard disk drives in the server.
• 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, save the EMC shield and
filler from the bay in case you later remove the device.

• For a complete list of supported optional devices for the server, go to:
To install a hot-swap hard disk drive, do the following:
Step 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.
Step 3. Install the hard disk drive into the drive bay:
a. Remove the hard-disk-drive filler 1. Keep the filler in a safe place. Make sure that the tray
handle 2 is in the open (unlocked) position.
b. Gently push the drive into the bay until the drive stops.
c. Close the tray handle to the locked position.
Figure 31. 2.5-inch hot-swap hard disk drive installation
Figure 32. 3.5-inch hot-swap hard disk drive installation
Step 4. Check the hard disk drive status LED to verify that the hard disk drive is operating properly. If the
yellow hard disk drive status LED of a drive is lit continuously, that drive is faulty and must be
reinstalled. 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. For additional information about RAID

operation and complete instructions for using the ServeRAID adapter, see the ServeRAID adapter
documentation.
Removing a simple-swap hard disk drive

Attention:
• To avoid damage to the hard disk drive connectors, make sure that the server cover is in place and fully
closed whenever you install or remove a hard disk drive.
• To ensure adequate system cooling, do not operate the server for more than two minutes without either a
hard disk drive or a filler installed in each bay.
To remove a simple-swap hard disk drive, do the following:
Step 3. Remove a simple-swap hard disk drive.
• For the 2.5-inch drive, slide the release latch 1 to the left and pull the hard disk drive out of the
drive bay at the same time.
Figure 33. 2.5-inch simple-swap hard disk drive removal
• For the 3.5-inch drive, remove the drive bay filler 1 from the server. Then, slide the release latch 2
to the right and pull the hard disk drive out of the drive bay at the same time.

Figure 34. 3.5-inch simple-swap hard disk drive removal
Step 4. Depending on your needs, install a new drive and then reinstall the filler or install the filler directly.
Installing a simple-swap hard disk drive

bay numbers are the same. For detailed information, refer to “Front view” on page 15.
Before you install a simple-swap SAS or SATA hard disk drive, read the following information. For a list of
supported hard disk drives, go to http://www.lenovo.com/ serverproven/.
• Locate the documentation that comes with the hard disk drive and follow those instructions in addition to
the instructions in this topic.
with the drive.
• Select the bay in which you want to install the drive.
• 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 device, be sure to set the SAS or SATA ID for that
device.
• You can install up to eight 2.5-inch or four 3.5-inch simple-swap SAS or SATA hard disk drives in the
server.
• 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, save the EMC shield and
filler from the bay in case you later remove the device.
• For a complete list of supported optional devices for the server, go to:
To install a simple-swap hard disk drive, do the following:
Step 3. Remove the filler from the empty drive bay.
Step 4. 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.
Step 5. Install the hard disk drive into the drive bay.

• For the 2.5-inch drive, slide the release latch 1 to the left. Then, gently push the drive into the bay
until the drive stops.
Figure 35. 2.5-inch simple-swap hard disk drive installation
• For the 3.5-inch drive, slide the release latch 2 to the right and gently push the drive into the bay
until the drive stops. Then, reinstall the filler.
Figure 36. 3.5-inch simple-swap hard disk drive installation
Removing the optical drive

To remove the optical drive, do the following:
Step 4. Press the release tab 1 as shown, hold the optical drive, and push the drive from the rear at the
same time to slide it out of the bay.

Figure 37. Optical drive removal
Step 5. Disconnect the optical drive cable.

a. Disconnect the optical drive cable from the system board.
b. Press the connector latch (on the left of the cable connector) as shown, grasp the cable
connector, and slide it to the right. Then, remove the optical drive cable from the connector
bracket on the chassis.
Attention: Do not disconnect the optical drive cable by using excessive force.
Figure 38. Optical drive cable disconnection
Step 6. Attach the drive retention clip that you removed from the optical drive to the side of the optical drive
filler. See “Installing the optical drive” on page 112. Then, slide the optical drive filler into the optical
drive bay until the optical drive filler clicks into place.

Figure 39. Optical drive filler installation
Installing the optical drive

The following tips describe the type of optical drives that the server supports and other information that you
must consider when you install an optical drive. For a list of supported optical drives, go to:
• Locate the documentation that comes with the optical drive and follow those instructions in addition to the
instructions in this topic.
with the optical drive.
• The server supports one ultra-slim SATA optical drive.
To install the optical drive, do the following:
Step 4. Remove the optical drive filler.
Step 5. Connect the optical drive cable. Make sure that the cable is not pinched and does not cover any
connectors or obstruct any components on the system board.
a. Align the cable connector with the connector bracket on the chassis, insert the cable
connector into the bracket, and slide it to the left until it is firmly seated.
b. Connect the other end of the cable to the system board.

Figure 40. Optical drive cable connection
Step 6. Touch the static-protective package that contains the new optical drive to any unpainted metal
surface on the server. Then, remove the optical drive from the package and place it on a static-
protective surface.
Step 7. Follow the instructions that come with the optical drive to set any jumpers or switches.
Step 8. Attach the drive retention clip that you removed from the optical drive filler to the side of the new
optical drive. Ensure that the alignment pins 1 on the retention clip are aligned with the
corresponding holes in the optical drive.
Figure 41. Optical drive retention clip installation
Step 9. Align the optical drive with the drive bay. Then, slide the optical drive into the bay until the optical
drive clicks into place.

Figure 42. Optical drive installation
Removing an adapter
To remove an adapter, do the following:
Step 3. Remove the PCI riser-card assembly. See “Removing the PCI riser-card assembly” on page 98.
Step 4. Disconnect cables from the adapter.
Step 5. Carefully grasp the adapter by its top edge and remove the adapter from the PCI riser-card
assembly.
Figure 43. Adapter removal
Installing an adapter
The following tips describe the types of adapters that the server supports and other information that you
must consider when you install an adapter:
• To confirm that the server supports the adapter that you are installing, go to:
• Locate the documentation that comes with the adapter and follow those instructions in addition to the
instructions in this topic.

• To ensure that any of your adapters function properly on UEFI-based servers, make sure that the adapter
firmware and supporting device drivers are updated to the latest version.
• The adapter slots are on the PCI riser-card assembly. You must first remove the PCI riser-card assembly
to access the adapter slots 1 and 2.
– 1 Dedicated to ServeRAID M1210 SAS/SATA Controller
– 2 Support one PCI Express Gen3 x8 half-length, full-height adapter
Figure 44. PCI riser-card assembly
Notes:
• If your adapter was previously configured, backup or record its configuration information, if possible,
before replacing the adapter. See the documentation for your adapter for information and instructions.
• If you are replacing a ServeRAID adapter, import your RAID configuration to the replacement adapter as a
foreign configuration after you finish the replacement. For more information, see https://www-947.ibm.com/
support/entry/portal/docdisplay?lndocid=migr-5086126.
To install an adapter, do the following:
Step 4. Touch the static-protective package that contains the adapter to any unpainted metal surface on
the server; then, remove the adapter from the package.
Step 5. 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.
Step 6. Connect the cables to the adapter.
Step 7. Position the adapter near the slot on the PCI riser-card assembly. Then, press the adapter firmly
into the PCI riser-card assembly. Ensure 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 2
on the PCI riser-card cage 1.

Figure 45. Adapter installation
Step 8. Route the adapter cables. Refer to “Internal cable routing” on page 157.
Step 9. Reinstall the PCI riser-card assembly. See “Installing the PCI riser-card assembly” on page 99.
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
damage the system board, the PCI riser-card assembly, or the adapter.
Notes:
• 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. For additional information about RAID operation
and complete instructions for using ServeRAID Manager, see the ServeRAID documentation on the
Lenovo ServeRAID Support CD.
• When you restart the server, you are prompted to import the existing RAID configuration to the new
ServeRAID SAS/SATA controller.
Removing a ServeRAID SAS/SATA controller memory module

Note: For brevity, in this documentation the Lenovo ServeRAID SAS/SATA controller is often referred to as
the SAS/SATA adapter or the ServeRAID adapter.
To remove a ServeRAID adapter memory module, do the following:
Step 4. Remove the ServeRAID adapter. See “Removing an adapter” on page 114.
Step 5. Grasp the memory module and lift to remove it from the ServeRAID adapter.

Figure 46. ServeRAID adapter memory module removal
Installing a ServeRAID SAS/SATA controller memory module

Note: For brevity, in this documentation the Lenovo ServeRAID SAS/SATA controller is often referred to as
the SAS/SATA adapter or the ServeRAID adapter.
To install a ServeRAID adapter memory module, do the following:
Step 4. Remove the ServeRAID adapter. See “Removing an adapter” on page 114.
Step 5. Touch the static-protective package that contains the memory module to any unpainted metal
surface on the server; then, remove the memory module from the package.
Step 6. Align the board-to-board connector 1 on the bottom of the memory module with the connector 2 on
the ServeRAID adapter. Ensure that the three mounting studs on the ServeRAID adapter are
aligned with the corresponding holes in the memory module. Carefully press the memory module
onto the ServeRAID adapter until the two connectors (1 and 2) are firmly joined.
Figure 47. ServeRAID adapter memory module installation

Step 7. Reinstall the ServeRAID adapter. See “Installing an adapter” on page 114.
Removing a RAID adapter battery or flash power module

Note: The RAID adapter battery or flash power module is supported on the 2.5-inch-drive server models
only.
To remove a RAID adapter battery or flash power module, do the following:
Step 3. Remove the RAID adapter battery or flash power module.
a. Remove the retainer.
b. Open the retention clip.
c. Pull the release tab outward.
d. Lift the battery or flash power module up to remove the battery or flash power module from the
holder.
Figure 48. RAID adapter battery or flash power module removal
Step 4. Disconnect the cable from the battery or flash power module.
Installing a RAID adapter battery or flash power module

When you install any RAID adapter that comes with batteries or flash power modules, sometimes it is
necessary to install the batteries or flash power modules in another location in the server to prevent the
batteries or flash power modules from overheating. Depending on your server model, a battery must be
installed remotely near the optical drive cage or the backplane.
Note: The RAID adapter battery or flash power module is supported on the 2.5-inch-drive server models
only.

To install a RAID adapter battery or flash power module in the server, do the following:
Step 4. Install a RAID adapter in the PCI riser-card assembly. See “Installing an adapter” on page 114.
Step 5. Connect one end of the cable to the connector on the RAID adapter. Make sure the relevant cables
pass through the cable clips and no cables cover or obstruct the battery holder.
Figure 49. RAID adapter battery or flash power module cable connection
Attention: Make sure that the cable is not pinched and does not cover any connectors or obstruct
any components on the system board.
Step 6. Connect the other end of the cable to the battery or flash power module. Then, remove the retainer
and open the retention clip of the battery or module holder.
Step 7. Install the battery or flash power module.
a. Pull the release tab outward.
b. Place the battery or flash power module into the holder and ensure that the holder engages the
battery or flash power module securely.
c. Lower and press down on the retention clip until it snaps in place to hold the battery or flash
power module firmly in place.
d. Install the retainer.

Figure 50. RAID adapter battery or flash power module installation
Note: The positioning of the remote battery or flash power module depends on the type of the
remote batteries or flash power modules that you install.
Removing a USB embedded hypervisor flash device

To remove a USB embedded hypervisor flash device, do the following:
Step 5. Locate the USB embedded hypervisor flash device connector on the system board. See “System-
board connectors” on page 21.
Step 6. Slide the lock bar on the flash device connector to the unlocked position and pull the USB flash
device out of the connector.

Figure 51. USB embedded hypervisor flash device removal
Installing a USB embedded hypervisor flash device

To install a USB embedded hypervisor flash device, do the following:
Step 5. Locate the USB embedded hypervisor flash device connector on the system board. See “System-
board connectors” on page 21.
Step 6. Align the USB flash device with the connector on the system board and push it into the connector
until it is firmly seated. Then, slide the lock bar on the flash device connector to the locked position.

Figure 52. USB embedded hypervisor flash device installation
Removing the front I/O assembly

The front I/O assembly contains an operator information panel and two cables.
To remove the front I/O assembly, do the following:
Step 3. Disconnect the USB cable and the operator information panel cable from the system board.
• To release the USB cable connector, press the release latch 1 on the top of the USB cable
connector. Then, pull out and disengage the USB cable connector from the USB connector on
the system board.
• To release the operator information panel cable connector, press the release latches 2 on both
sides of the cable connector. Then, pull out and disengage the cable connector from the
operator information panel connector on the system board.

Figure 53. USB cable and operator information panel cable disconnection
Step 4. Locate the release tab on the rear of the front I/O assembly. Then, lift the release tab and carefully
pull out the front I/O assembly.
Figure 54. Front I/O assembly removal
Step 5. Install a new front I/O assembly. See “Installing the front I/O assembly” on page 123.
Installing the front I/O assembly

The front I/O assembly contains an operator information panel and two cables. If you have removed the front
I/O assembly, install a new one before turning on the server.
To install the front I/O assembly, do the following:
Step 1. Carefully push the front I/O assembly into the server as shown until the front I/O assembly clicks
into place.

Figure 55. Front I/O assembly installation
Step 2. Reconnect the USB cable and the operator information panel cable to the connectors on the
system board. Make sure the relevant cables pass through the cable clips.
Removing the operating temperature enhancement kit

To remove the operating temperature enhancement kit, do the following:
Step 4. Disconnect the operating temperature enhancement kit connector from the system board.
Figure 56. Operating temperature enhancement kit cable disconnection for 2.5-inch-drive model

Figure 57. Operating temperature enhancement kit cable disconnection for 3.5-inch-drive model
Step 5. Detach the operating temperature enhancement kit 1 from the slot 2 on the hard disk drive cage.
Figure 58. Operating temperature enhancement kit removal
Installing the operating temperature enhancement kit

To install the operating temperature enhancement kit, do the following:
Step 4. Connect the operating temperature enhancement kit connector to the system board.
Step 5. Route the cable along the chassis. Make sure the relevant cables pass through the cable clips.

Figure 59. Operating temperature enhancement kit cable connection for 2.5-inch-drive model
Figure 60. Operating temperature enhancement kit cable connection for 3.5-inch-drive model
Attention: Make sure that the cable is not pinched and does not cover any connectors or obstruct
any components on the system board.
Step 6. Slide the operating temperature enhancement kit 1 into the slot 2 on the hard disk drive cage until
the operating temperature enhancement kit locks into place with an audible click.

Figure 61. Operating temperature enhancement kit installation
Removing a system fan

To remove a system fan, do the following:
Step 1. Check the IMM2.1 event log to find out which fan needs to be replaced. Refer to Appendix A
“Integrated Management Module 2.1 (IMM2.1) error messages” on page 173 for the error
messages.
Step 5. Disconnect the fan cable from the system board. Record the routing of the fan cable; you will have
to route the fan cable the same way when you install the fan.
Step 6. Grasp the top of the fan with your index finger and thumb and lift the fan out of the server.
Figure 62. System fan removal

Installing a system fan
To install a system fan, do the following:
Step 4. Position the new 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.
Step 5. Insert the fan into the bracket. Then, route the fan cable into the fan cable slot in the fan bracket.
Make sure that each of the gray soft tabs on the fan is fully seated in its slot in the fan bracket.
Figure 63. System fan installation
Step 6. Connect the new fan cable to the system board. To locate the fan connectors on the system board,
see “System-board connectors” on page 21.
Removing the coin-cell battery

The following tips describe information that you must consider when removing the coin-cell battery.
• Lenovo has designed this product with your safety in mind. The lithium coin-cell battery must be handled
correctly to avoid possible danger. If you replace the coin-cell battery, you must adhere to the following
instructions.
Note: In the U.S., call 1-800-IBM-4333 for information about battery disposal.
• If you replace the original lithium battery with a heavy-metal battery or a battery with heavy-metal
components, be aware of the following environmental consideration. Batteries and accumulators that
contain heavy metals must not be disposed of with normal domestic waste. They will be taken back free
of charge by the manufacturer, distributor, or representative, to be recycled or disposed of in a proper
manner.
• To order replacement batteries, call 1-800-IBM-SERV within the U.S., and 1-800-465-7999 or 1-800-465-
6666 within Canada. Outside the U.S. and Canada, call your support center or business partner.

Note: After you replace the coin-cell battery, you must reconfigure the server and reset the system date
and time.
CAUTION:
When replacing the lithium battery, use only Part Number 33F8354 or an equivalent type battery
recommended by the manufacturer. If your system has a module containing a lithium battery,
replace it only with the same module type made by the same manufacturer. The battery contains
lithium and can explode if not properly used, handled, or disposed of.
Do not:
– Throw or immerse into water
– Heat to more than 100°C (212°F)
– Repair or disassemble
Note: After you remove the coin-cell battery, you need to install a new one. See “Installing the coin-cell
battery” on page 129.
To remove the coin-cell battery, do the following:
Step 3. If necessary, remove the air baffle. See “Removing the air baffle” on page 95.
Step 4. Locate the coin-cell battery, see “System-board connectors” on page 21.
Step 5. Remove the coin-cell battery.
Attention:
• Failing to remove the coin-cell battery properly might damage the socket on the system board.
Any damage to the socket might require replacing the system board.
• Do not tilt or push the coin-cell battery by using excessive force.
Figure 64. Coin-cell battery removal
Step 6. Dispose of the coin-cell battery as required by local ordinances or regulations.
Installing the coin-cell battery

The following tips describe information that you must consider when installing the coin-cell battery.

• Follow any special handling and installation instructions that come with the coin-cell battery.
• Lenovo has designed this product with your safety in mind. The lithium battery must be handled correctly
to avoid possible danger. If you install the coin-cell battery, you must adhere to the following instructions.
Note: In the U. S., call 1-800-IBM-4333 for information about battery disposal.
• If you replace the original lithium battery with a heavy-metal battery or a battery with heavy-metal
components, be aware of the following environmental consideration. Batteries and accumulators that
contain heavy metals must not be disposed of with normal domestic waste. They will be taken back free
of charge by the manufacturer, distributor, or representative, to be recycled or disposed of in a proper
manner.
• To order replacement batteries, call 1-800-IBM-SERV within the U.S., and 1-800-465-7999 or 1-800-465-
6666 within Canada. Outside the U.S. and Canada, call your support center or business partner.
Note: After you install the coin-cell battery, you must reconfigure the server and reset the system date
and time.
CAUTION:
When installing the lithium battery, use only Part Number 33F8354 or an equivalent type battery
recommended by the manufacturer. If your system has a module containing a lithium battery, install
it only with the same module type made by the same manufacturer. The battery contains lithium
and can explode if not properly used, handled, or disposed of.
Do not:
– Throw or immerse into water
– Heat to more than 100°C (212°F)
– Repair or disassemble
To install the coin-cell battery, do the following:
Step 1. Install the new coin-cell battery. Ensure that the coin-cell battery retainer holds the battery
securely.
Figure 65. Coin-cell battery installation
Step 3. Start Setup Utility and reset the configuration:
a. Set the system date and time.

b. Set the power-on password.
c. Reconfigure the server.
For more information, see “Starting the Setup Utility program” on page 29.
Removing the fixed power supply

When you remove the fixed power supply, observe the following precautions.
CAUTION:
Note: After you remove the fixed power supply, you need to install a new one. See “Installing the fixed
power supply” on page 132.
To remove the fixed power supply, do the following:
Step 3. Disconnect the power-supply cables from the connectors on the system board and internal
devices. Then, disengage the cables from any retention clips.
Note: Record the routing of all power-supply cables; you will route the power-supply cables the
same way when you install the power supply.
Step 4. Remove the fixed power supply.
a. Remove the screws that secure the power supply to the rear of the chassis.
b. Push the power supply toward the front of the server until the power supply has disengaged
from the chassis.
c. Lift the power supply out of the chassis.

Figure 66. Fixed power supply removal
Installing the fixed power supply

When you install the fixed power supply, observe the following precautions.
CAUTION:
To install the fixed power supply, do the following:
Step 1. Install the fixed power supply.

a. Position the power supply on the chassis.
b. Push the power supply toward the rear of the server until the power supply engages the
chassis.
c. Install the screws to secure the power supply to the chassis.

Figure 67. Fixed power supply installation
Step 2. Connect the internal power-supply cables from the power supply to the power supply connector
and CPU power connector on the system board. To locate the power connectors on the system
board, see “System-board connectors” on page 21.
Step 3. Route the internal power-supply cables, securing them with the retention clips.
Step 4. Test the power supply:
a. Connect one end of the ac power cord for the new power supply into the power supply
connector, and connect the other end of the power cord into a properly grounded electrical
outlet. Make sure that the standby power LED on the system board is lit. See “System-board
LEDs” on page 23.
b. 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.
Step 5. Turn off the server and disconnect the ac power cord.
Step 7. Press the power-control button. Make sure that the power-on LED on the front of the server is lit.
Removing a hot-swap power supply

When you remove a power supply, observe the following precautions.
CAUTION:
power source.

2
1
CAUTION:
Figure 68. Hot-swap power supply label on the cover
To remove a hot-swap power supply, do the following:
Attention: This type of power supply is hot-swap only when two power supplies are installed for
redundancy. If only one power supply is installed, you must turn off the server first before removing the
power supply.
Step 1. If the server is in a rack, pull back the cable management arm to gain access to the rear of the
server and the power supply.
Step 2. Disconnect the power cord from the hot-swap power supply.
Step 3. Press the release tab toward the handle and carefully pull the handle at the same time to slide the
hot-swap power supply out of the chassis.

Figure 69. Hot-swap power supply removal
Step 4. Install the power-supply filler or a new power supply to cover the power supply bay. See “Installing
a hot-swap power supply” on page 135.
Installing a hot-swap power supply

The following tips describe the type of power supply that the server supports and other information that you
must consider when you install a power supply:
• For 460-watt power-supply server models, the standard shipping has only one 460-watt power supply
installed in the server. For redundancy and hot-swap support, you must install an additional 460-watt hot-
swap power supply. Certain customized models might be shipped with two power supplies installed.
• Make sure that the devices that you are installing are supported. For a list of supported optional devices
for the server, go to http://www.lenovo.com/ serverproven/.
2
1
CAUTION:

Figure 70. Hot-swap power supply label on the cover
To install a hot-swap power supply, do the following:
Step 1. Remove the power-supply filler. Then, slide the hot-swap power supply into the bay until the
release latch clicks into place.
Important: To ensure proper cooling during normal server operation, both of the power supply
bays must be occupied. This means that each bay must have a power supply installed; or one has
a power supply installed and the other has a power-supply filler installed.
Figure 71. Hot-swap power supply installation
Step 2. Connect one end of the power cord to the new power supply connector; then, connect the other
end of the power cord into a properly grounded electrical outlet.
Step 3. If the server is turned off, turn on the server. Make sure that the ac power LED on the power supply
is lit, indicating that the power supply is operating properly. If the server is turned on, make sure
that the dc power LED on the power supply is lit also.
Removing the PCI riser card from the PCI riser-card assembly
To remove the PCI riser card from the PCI riser-card assembly, do the following:
Step 4. Remove the screws that secure the PCI riser card to the riser card bracket. Then, remove the PCI
riser card.

Figure 72. PCI riser card removal
Step 5. Install a new PCI riser card to the PCI riser-card assembly. See “Installing the PCI riser card to the
PCI riser-card assembly” on page 137.
Installing the PCI riser card to the PCI riser-card assembly

If you have removed PCI riser card from the PCI riser-card assembly, install a new PCI riser card to the PCI
riser-card assembly before turning on the server.
To install the PCI riser card to the PCI riser-card assembly, do the following:
Step 1. Align the holes in the PCI riser card with the holes in the riser-card bracket. Then, install the screws
to secure the PCI riser card to the riser-card bracket.
Figure 73. PCI riser-card bracket installation
Step 2. If needed, install an adapter. See “Installing an adapter” on page 114. Then, connect the cables for
the adapter.
Step 3. Reinstall the PCI riser-card assembly. See “Installing the PCI riser-card assembly” on page 99.

Removing the 2.5-inch hot-swap hard-disk-drive backplane
Note: After you remove the 2.5-inch hot-swap hard-disk-drive backplane, you need to install a new one. See
“Installing the 2.5-inch hot-swap hard-disk-drive backplane” on page 138.
To remove the 2.5-inch hot-swap hard-disk-drive backplane, do the following:
Step 3. Remove the hard disk drives or fillers out of the server. See “Removing a hot-swap hard disk drive”
on page 105.
Step 4. Disconnect all cables from the hard-disk-drive backplane.
Step 5. Lift the blue tabs on the backplane to disengage and remove the backplane from the chassis.
Figure 74. 2.5-inch hot-swap hard-disk-drive backplane removal
Installing the 2.5-inch hot-swap hard-disk-drive backplane

The following illustration shows contents of the second 2.5-inch hard-disk-drive backplane upgrade kit:
Figure 75. The second 2.5-inch hard-disk-drive backplane upgrade kit
1 Mini-SAS signal cable connector

2 Power connector
To install the 2.5-inch hot-swap hard-disk-drive backplane, do the following:
Step 1. Align the backplane with the backplane alignment slots in the chassis. Then, carefully lower the
hard-disk-drive backplane until it is fully seated in the chassis.
Figure 76. 2.5-inch hot-swap hard-disk-drive backplane installation
Step 2. Reconnect all cables that you removed from the hard-disk-drive backplane.
Step 3. If you need to install the second backplane, repeat step 4.
Step 4. Install a RAID adapter. See “Installing an adapter” on page 114.
Step 5. Connect power and signal cables. Refer to the following topics:
• “Hot-swap HDD cable connection: ServeRAID SAS/SATA controller and hot-swap power
supply” on page 166
• “Hot-swap HDD cable connection: ServeRAID SAS/SATA controller and fixed power supply” on
page 162
Step 6. Reinstall the hard disk drives and fillers. See “Installing a hot-swap hard disk drive” on page 106.
Removing the 2.5-inch simple-swap hard-disk-drive backplate assembly

Note: After you remove the 2.5-inch simple-swap hard-disk-drive backplate assembly, you need to install a
new one. See “Installing the 2.5-inch simple-swap hard-disk-drive backplate assembly” on page 140.
To remove the 2.5-inch simple-swap hard-disk-drive backplate assembly, do the following:
Step 3. Remove the PCI riser-card assembly if installed. See “Removing the PCI riser-card assembly” on
page 98.
Step 4. Disconnect the cables from the RAID adapter or system board. See “Internal cable routing” on
page 157. Then, remove the corresponding cables from the cable clips.

Step 5. Remove the installed hard disk drives or fillers from the drive bays. See “Removing a simple-swap
hard disk drive” on page 108.
Step 6. Grasp the blue tabs on the backplate assembly to lift the backplate assembly from the chassis.
Figure 77. 2.5-inch simple-swap hard-disk-drive backplate assembly removal
Installing the 2.5-inch simple-swap hard-disk-drive backplate assembly

There are three types of 2.5-inch simple-swap hard-disk-drive backplate assemblies. In the following
illustrations, type a and b are for server models with RAID adapters and type c is for server models with
onboard software RAID configuration.
Figure 78. 2.5-inch simple-swap hard-disk-drive backplate assemblies
1 Power connector
2 Mini-SAS signal connector
To install the 2.5-inch simple-swap hard-disk-drive backplate assembly, do the following:

Step 1. Align the backplate assembly with the backplate assembly alignment slots in the chassis. Then,
carefully lower the backplate assembly into the chassis until it is seated firmly.
Figure 79. 2.5-inch simple-swap hard-disk-drive backplate assembly installation
Step 2. Connect the cables to the RAID adapter or system board. Refer to the following topics:
• “Simple-swap HDD cable connection: onboard RAID” on page 160
• “Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and fixed power supply”
on page 164
• “Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and redundant power
Step 3. Reinstall the hard disk drives or fillers. See “Installing a simple-swap hard disk drive” on page 109.
Removing the 3.5-inch hot-swap hard-disk-drive backplane

Note: After you remove the 3.5-inch hot-swap hard-disk-drive backplane, you need to install a new one. See
“Installing the 3.5-inch hot-swap hard-disk-drive backplane” on page 142.
To remove the 3.5-inch hot-swap hard-disk-drive backplane, do the following:
page 98.
Step 4. Remove the installed hard disk drives or fillers from the drive bays. See “Removing a hot-swap hard
disk drive” on page 105.
Step 5. Pivot the retention latches on the chassis as shown in the following illustration. Then, carefully pull
the backplane assembly outwards and lift it up to remove it out of the chassis.

Figure 80. 3.5-inch hot-swap hard-disk-drive backplane removal
Step 6. Disconnect all cables from the hard-disk-drive backplane.
Installing the 3.5-inch hot-swap hard-disk-drive backplane

To install the 3.5-inch hot-swap hard-disk-drive backplane, do the following:
Step 1. Connect cables to the hard-disk-drive backplane.

Step 2. Carefully lower the backplane assembly into the alignment slots in the chassis. Then, close the
retention latches to secure the backplane to the chassis.
Figure 81. 3.5-inch hot-swap hard-disk-drive backplane installation

Step 3. Connect all cables to the system board or RAID adapter. See “Hot-swap HDD cable connection:
ServeRAID SAS/SATA controller and fixed power supply” on page 162.
Step 4. Install the hard disk drives and fillers. See “Installing a hot-swap hard disk drive” on page 106.
Removing the 3.5-inch simple-swap hard-disk-drive backplate assembly

Note: After you remove the 3.5-inch simple-swap hard-disk-drive backplate assembly, you need to install a
new one. See “Installing the 3.5-inch simple-swap hard-disk-drive backplate assembly” on page 143.
To remove the 3.5-inch simple-swap hard-disk-drive backplate assembly, do the following:
page 98.
Step 4. Disconnect the cables from the RAID adapter or system board. See “Internal cable routing” on
page 157. Then, remove the corresponding cables from the cable clips.
Step 5. Remove the installed hard disk drives or fillers from the drive bays. See “Removing a simple-swap
hard disk drive” on page 108.
Step 6. Pivot the retention latches on the chassis upward. Then, carefully pull the backplate assembly
outwards and lift it up to remove it out of the chassis.
Figure 82. 3.5-inch simple-swap hard-disk-drive backplate assembly removal
Installing the 3.5-inch simple-swap hard-disk-drive backplate assembly

There are two types of 3.5-inch simple-swap hard-disk-drive backplate assemblies. In the following
illustration, type b is for server models with onboard software RAID configuration.

1 Power connector
2 Mini-SAS signal connector
To install the 3.5-inch simple-swap hard-disk-drive backplate assembly, do the following:
Step 1. Carefully lower the backplate assembly into the alignment slots in the chassis. Then, close the
retention latches to secure the backplate assembly to the chassis.
Figure 84. 3.5-inch simple-swap hard-disk-drive backplate assembly installation
Step 2. Connect cables to the RAID adapter or system board. Refer to the following topics:
• “Simple-swap HDD cable connection: onboard RAID” on page 160

• “Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and redundant power
• “Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and fixed power supply”
on page 164
Step 3. Install the hard disk drives and fillers. See “Installing a simple-swap hard disk drive” on page 109.
Removing and installing Tier 2 CRUs

This section provides information about removing and installing Tier 2 CRUs.
You may install a Tier 2 CRU yourself or request Lenovo to install it, at no additional charge, under the type of
warranty service that is designated for your server. The illustrations in this document might differ slightly from
your hardware.
Removing the microprocessor and heat sink (Trained technician only)

The following notes describe the type of microprocessor that the server supports and other information that
you must consider when you install or remove a microprocessor and heat sink:
• The server supports one Intel land grid array (LGA) 1151 dual-core or quad-core microprocessor. The
type, speed, and L3 cache of the microprocessor depends on the server model.
• Read the documentation that comes with the microprocessor to determine whether you have to update
the server firmware. To download the most current level of server firmware, go to http://www.lenovo.com/
support and https://datacentersupport.lenovo.com.
• The microprocessor uses an integrated voltage regulator on the system board.
Attention:
• 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.
• Dropping the microprocessor during installation or removal can damage the contacts.
• 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.
• The pins on the sockets are fragile. Any damage to the pins might require replacing the system board.
• Removing the heat sink from the microprocessor destroys the even distribution of the thermal grease, you
must wipe off the thermal grease with the alcohol wipes and reapply clean thermal grease. See “Thermal
grease” on page 149.
• After you remove a new microprocessor or a new heat sink, you need to install a new one. See “Installing
the microprocessor and heat sink (Trained technician only)” on page 147.
To remove the microprocessor and heat sink, do the following:
Step 4. Remove the heat sink.
CAUTION:

The heat sink might become very hot during normal operation. Allow time for the heat sink to
cool down before you touch it.
a. Use a screwdriver to loosen the captive screws 1 by rotating screws until each screw is loose.
b. Alternate among the screws until they break the seal with the microprocessor.
c. Gently twist the heat sink to free it from the microprocessor and then lift the heat sink off the
system board.
Figure 85. Heat sink removal
Step 5. Place the heat sink on its side on a clean, flat surface after removal.
Step 6. Remove the microprocessor.
a. Open the microprocessor retention latch by gently pressing down the handle a little bit and
then pushing the handle outward.
b. Open the microprocessor bracket. Keep the bracket in the open position.
c. Hold the microprocessor by its edges and carefully lift the microprocessor straight up and out
of the socket.
Attention: Handle the microprocessor carefully. Dropping the microprocessor during removal can
damage the contacts. In addition, contaminants on the microprocessor contacts, such as oil from
your skin, can cause connection failures between the contacts and the socket.

Figure 86. Microprocessor removal
Step 7. Place the microprocessor on a static-protective surface.
Attention: The pins on the sockets are fragile. Any damage to the pins might require replacing the
system board.
Installing the microprocessor and heat sink (Trained technician only)

The following notes describe the type of microprocessor that the server supports and other information that
you must consider when you install a microprocessor and heat sink:
• The server supports one Intel land grid array (LGA) 1151 dual-core or quad-core microprocessor. The
type, speed, and L3 cache of the microprocessor depends on the server model.
• Read the documentation that comes with the microprocessor to determine whether you have to update
the server firmware. To download the most current level of server firmware, go to http://www.lenovo.com/
support and https://datacentersupport.lenovo.com.
• The microprocessor uses an integrated voltage regulator on the system board.
• The microprocessor speeds are automatically set for this server; therefore, you do not have to set any
microprocessor frequency-selection jumpers or switches.
• 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 149.
Note: Removing the heat sink from the microprocessor destroys the even distribution of the thermal
grease and requires reapplying the thermal grease.
Attention:
• 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.
• Dropping the microprocessor during installation or removal can damage the contacts.
• The microprocessor contacts are fragile. 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.
• The pins on the sockets are fragile. Any damage to the pins might require replacing the system board.

• 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 94.
• The microprocessor fits only one way on the socket.
• Removing the heat sink from the microprocessor destroys the even distribution of the thermal grease, you
must wipe off the thermal grease with the alcohol wipes and reapply clean thermal grease. See “Thermal
grease” on page 149.
To install the microprocessor and heat sink, do the following:
Install the microprocessor.

a. Align the microprocessor with the socket (note the alignment marks 1 and the position of the notches)
and carefully place the microprocessor on the socket.
b. Close the microprocessor bracket frame.
c. Close the microprocessor retention latch by securing the handle back to its position.
Figure 87. Microprocessor installation
Install the heat sink on the microprocessor.
Attention: Do not touch the thermal grease on the bottom of the heat sink. Touching the thermal grease will
contaminate it. If the thermal grease on the microprocessor or heat sink becomes contaminated, you must
wipe off the contaminated thermal grease on the microprocessor or heat sink with the alcohol wipes and
reapply clean thermal grease to the heat sink.
a. Align the heat sink so that the arrows on the label point toward the DIMMs and place the heat sink on
top of the microprocessor, thermal grease side down.
b. Align the screws on the heat sink with the screw holes in the system board.
c. Tighten the screws 1 with a screwdriver, alternating among the screws until they are tight. If possible,
each screw should be rotated two full rotations at a time. Repeat until the screws are tight.
Attention: When the two screws that are closer to the rear of the server are tightened, the screw heads
are not level with the surface of the heat sink. Do not overtighten the screws by using excessive force.

Figure 88. Heat sink installation
Thermal grease
The thermal grease must be replaced whenever the heat sink has been removed from the top of the
microprocessor. Use the following information to replace damaged or contaminated thermal grease on the
microprocessor and heat sink.
Read “Handling static-sensitive devices” on page 94.
To replace damaged or contaminated thermal grease on the microprocessor and heat sink, do the following:
Step 1. Place the heat sink on a clean work surface.

Step 2. Remove the cleaning pad from its package and unfold it completely.
Step 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.

Step 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.
Step 5. Use the thermal-grease syringe to place nine uniformly spaced dots 1 of 0.02 mL each on the top of
the microprocessor or on the bottom of the heat sink. The outermost dots must be within
approximately 5 mm (0.2 inches) of the edge of the microprocessor. This is to ensure uniform
distribution of the grease.

Figure 89. Thermal grease on the microprocessor
Figure 90. Thermal-grease syringe
Note: One tick mark on the syringe is 0.01 mL. If the grease is properly applied, approximately half
(0.22 mL) of the grease will remain in the syringe.
Step 6. Install the heat sink onto the microprocessor. See “Installing the microprocessor and heat sink
(Trained technician only)” on page 147.
Removing the power distribution board cover

To remove the power distribution board cover, do the following:
Step 3. Remove any connected SAS/SATA signal cable and all other cables that pass through the power
distribution board cover. See “Internal cable routing” on page 157.
Step 4. Remove the screw from the power distribution board cover. Then, lift the power distribution board
cover up to remove it from the server.

Figure 91. Power distribution board cover removal
Step 5. Reinstall the power distribution board cover or install a new one. See “Installing the power
distribution board cover” on page 151.
Installing the power distribution board cover

If you have moved the power distribution board cover, reinstall it or install a new one if the old one is broken.
To install the power distribution board cover, do the following:
Step 1. Install the power distribution board cover.

a. Align the screw hole in the power distribution board cover with the mounting stud on the
chassis.
b. Lower the power distribution board cover onto the power distribution board.
c. Install the screw to secure the power distribution board cover.

Figure 92. Power distribution board cover installation
Removing the power distribution board

To remove the power distribution board, do the following:
Step 3. Remove the power distribution board cover. See “Removing the power distribution board cover” on
page 150. Then, Loosen the cables from the cable tie.
Step 4. Disconnect the power distribution board cables from the system board. Then, disconnect all other
cables on the system board that block the removal of the power distribution board.
Step 5. Remove the screws. Then, lift the power distribution board up to remove it from the server.
Figure 93. Power distribution board removal

Step 6. Install a new power distribution board. See “Installing the power distribution board” on page 153.
Installing the power distribution board

If you have moved the power distribution board, install a new one before turning on the server.
To install the power distribution board, do the following:
Step 1. Align the screw holes in the power distribution board with the mounting studs on the chassis and
lower the power distribution board onto the chassis. Then, install the screws to secure the power
distribution board.
Figure 94. Power distribution board installation
Step 2. Connect cables to the power distribution board.

Step 3. Install the power distribution board cover. See “Installing the power distribution board cover” on
page 151.
Step 4. Connect the cables to the power supply connector, microprocessor power connector, and power
distribution board connector on the system board. See “System-board connectors” on page 21.
Attention: When connecting the cable to the system board, do not grab the wires. Grab the
connector to vertically connect the cable to the system board.
Figure 95. Connecting the power cable connector to the system board

Removing the system board

Before you start, notice the following information:
• After 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 CD image. Make sure that you have the latest
firmware or a copy of the pre-existing firmware before you proceed.
• When you replace the system board, make sure that you remove the Integrated Management Module 2.1
(IMM2.1) Advanced Upgrade and place it on the new system board.
• Before you replace the system board, make sure that you back up any Features on Demand (FoD) keys
that were enabled. Reactivate FoD after replacing the system board. To activate FoD and install activation
keys automatically, refer to the instructions in the Lenovo Features on Demand User's Guide. To download
the document, go to https://fod.lenovo.com/lkms, log in, and click Help.
Note: After you remove the system board, you need to install a new one. See “Installing the system board”
on page 155.
To remove the system board, do the following:
Step 5. Record where the cables are connected to the system board; then, disconnect them.
Attention: Disengage all latches, cable clips, release tabs, or locks on cable connectors
beforehand. See “Internal cable routing” on page 157. Failing to release them before removing the
cables will damage the cable connectors on the system board. Any damage to the cable
connectors may require replacing the system board.
Step 6. Remove any of the following components that are installed on the system board and put them in a
safe, static-protective place:
• Adapters (see “Removing an adapter” on page 114)
• DIMMs (see “Removing a DIMM” on page 101)
• Microprocessor and heat sink (see “Removing the microprocessor and heat sink (Trained
technician only)” on page 145)
Notes:
– Do not allow the thermal grease to come in contact with anything. Contact with any surface
can compromise the thermal grease and the microprocessor socket.
– Keep each heat sink paired with its microprocessor for reinstallation A mismatch between the
microprocessor and its original heat sink can require the installation of a new heat sink.
• The RAID battery holder (see “Removing the flash power module holder” on page 100)
Step 7. Remove the system board.
a. Remove the nine screws that secure the system board to the chassis, and put the screws in a
safe place.
b. Hold the two corners 1 of the system board carefully. Avoid touching the connectors on the
system board.
c. Lift and tilt the system board upwards and slightly pull the system board towards the front of
the server.

d. Lift and remove the system board from the server carefully.
Note: When you remove the system board from the server, avoid touching the cable clips on the
side of the chassis and the connectors on the system board. Do not damage any surrounding
components inside the chassis.
Figure 96. System board removal
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.
Before returning the failing system board, ensure that you remove the microprocessor socket cover from the
new system board and install it onto the failing system board.
Installing the system board

Before you start, notice the following information:
• After you reassemble the components in the server, route all cables carefully so that they are not exposed
to excessive pressure.
• When you install the system board, ensure that you remove the Integrated Management Module 2.1
(IMM2.1) Advanced Upgrade from the failing system board and place it on the new system board. For
information about the Advanced Upgrade, see “Using the remote presence and blue-screen capture
features” on page 36.
• Some cluster solutions require specific code levels or coordinated code updates. If the device is part of a
cluster solution, verify that the latest level of code is supported for the cluster solution before you update
the code.
To install the system board, do the following:
Step 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.

Note: When you are holding or installing the system board in the server, avoid touching the cable
clips on the side of the chassis and the connectors on the system board. Do not damage any
surrounding components inside the chassis.
Step 2. Hold the two corners 1 of the system board carefully, align the screw holes in the system board with
the corresponding mounting studs on the chassis, and then install the nine screws that you
removed.
Figure 97. System board installation
Step 3. Install any of the following components that you removed from the failing system board:
Note: Make sure that none of the server cables are caught under the system board.
1. Microprocessor and heat sink (see “Installing the microprocessor and heat sink (Trained
technician only)” on page 147)
2. DIMMs (see “Installing a DIMM” on page 104)
3. Adapters (see “Installing an adapter” on page 114)
4. The RAID battery holder (see “Installing flash power module holder” on page 101).
Step 5. Remove the microprocessor socket cover from the new system board and install it onto the failing
system board.
Step 6. 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.
For more information, see “Using the Setup Utility program” on page 29.
Step 7. Either update the server with the latest RAID firmware or restore the pre-existing firmware from a
CD image. See “Updating the firmware” on page 25.
Step 8. Update the UUID. See “Updating the Universal Unique Identifier (UUID)” on page 40.

Step 9. Update the DMI/SMBIOS. See “Updating the DMI/SMBIOS data” on page 41.
Step 10. Reactivate FoD. To activate FoD and install activation keys automatically, refer to the instructions is
in the Features on Demand User's Guide. To download the document, go to https://fod.lenovo.com/
lkms, log in, and click Help.
Internal cable routing

This section provides information about routing the cables when you install some components in the server.
To connect cables, observe the following instructions:

• Turn off the server before you connect or disconnect any internal cables.
• See the documentation that comes with any external devices for additional cabling instructions. It might
be easier for you to route cables before you connect the devices to the server.
• Cable identifiers of some cables are printed on the cables that come with the server and optional devices.
Use these identifiers to connect the cables to the correct connectors.
Optical drive cable connection

This topic provides information about the internal cable routing for the optical drive.
Notes:
• Ensure that the cable is not pinched and does not cover any connectors or obstruct any components on
the system board.
• Ensure the relevant cables pass through the cable clips.
To connect the optical drive to the system board, do the following:

1. Insert one end of the optical drive cable into the slot in the connector bracket. Then slide the connector
to the left as shown until it is firmly seated in the bracket.
2. Connect the other end of the optical drive cable to the system board.
Figure 98. Optical drive cable connection

Operating temperature enhancement kit cable connection
This topic provides information about the internal cable routing for the operating temperature enhancement
kit.
Notes:
the system board.
Figure 99. Operating temperature enhancement kit cable connection for the 2.5-inch hard disk drive model
Figure 100. Operating temperature enhancement kit cable connection for the 3.5-inch hard disk drive model

Fixed power supply cable connection
This topic provides information about the cable routing for the fixed power supply.
Notes:
the system board.
• 1: Connect to the power connector on the system board.
• 2: Connect to the microprocessor power connector on the system board.
See “System-board connectors” on page 21.
Figure 101. Fixed power supply cable connection
Front USB module and operator information panel cable connection

This topic provides information about the internal cable routing for the front USB module and the operator
information panel.
Notes:
the system board.
• 1: Press the release latch and connect to the front USB connector on the system board.
• 2: Press evenly on the release latches and connect to the operator information panel connector on the
system board.

Figure 102. Operator information panel cable connection
Simple-swap HDD cable connection: onboard RAID

This topic provides information about the internal cable connection for the simple-swap hard disk drive with
onboard RAID.
• 1: Connect to the backplane power connector on the system board and the power connector on the hard-
disk-drive backplate assembly.
• 2: Connect to the Mini-SAS connector on the system board and the four connectors of the Mini-SAS cable
to the hard-disk-drive backplate assembly.
Notes:
• The Mini-SAS cable has been installed to the hard-disk-drive backplate assembly by default.
the system board.
• Ensure the power cable and Mini-SAS cable pass through the cable clips.

Figure 103. Simple-swap HDD cable connection: 3.5-inch, onboard RAID, and fixed power supply
Figure 104. Simple-swap HDD cable connection: 2.5-inch, onboard RAID, and fixed power supply

Figure 105. Simple-swap HDD cable connection: 2.5-inch, onboard RAID, and hot-swap power supply
Hot-swap HDD cable connection: ServeRAID SAS/SATA controller and fixed power
supply
disk-drive backplane.
• 2: Connect to the connector 0 on the ServeRAID SAS/SATA controller and the Mini-SAS connector on the
hard-disk-drive backplane.
Notes:
the system board.

Figure 106. Hot-swap HDD cable connection: 2.5-inch, ServeRAID SAS/SATA controller installed on the right side
Figure 107. Hot-swap HDD cable connection: 2.5-inch, ServeRAID SAS/SATA controller installed on the left side

Figure 108. Hot-swap HDD cable connection: 3.5-inch, ServeRAID SAS/SATA controller installed on the right side
Figure 109. Hot-swap HDD cable connection: 3.5-inch, ServeRAID SAS/SATA controller installed on the left side
Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and fixed

power supply
• 2: Connect to the connector 0 on the ServeRAID SAS/SATA controller and the four connectors on the
hard-disk-drive backplate assembly.
Notes:

the system board.
Figure 110. Simple-swap HDD cable connection: 2.5-inch, ServeRAID SAS/SATA controller installed on the right side
Figure 111. Simple-swap HDD cable connection: 2.5-inch, ServeRAID SAS/SATA controller installed on the left side

Figure 112. Simple-swap HDD cable connection: 3.5-inch, ServeRAID SAS/SATA controller installed on the right side
Figure 113. Simple-swap HDD cable connection: 3.5-inch, ServeRAID SAS/SATA controller installed on the left side
Hot-swap HDD cable connection: ServeRAID SAS/SATA controller and hot-swap

power supply
disk-drive backplane.
• 2: Connect to the connector 0 on the ServeRAID SAS/SATA controller and the Mini-SAS connector on the
hard-disk-drive backplane.
Notes:

the system board.
Figure 114. Hot-swap HDD cable connection: four HDDs, ServeRAID SAS/SATA controller installed on the right side
Figure 115. Hot-swap HDD cable connection: four HDDs, ServeRAID SAS/SATA controller installed on the left side
To connect cables for the server models with eight hot-swap hard disk drives, do the following:

Figure 116. Cables for the 2.5-inch hard-disk-drive backplanes
1. Connect the cable labeled with 0 to the connector 0 on the ServeRAID SAS/SATA controller and the hot-
swap hard-disk-drive backplane 1.
2. Connect the cable labeled with 1 to the connector 1 on the ServeRAID SAS/SATA controller and the hot-
swap hard-disk-drive backplane 2.
3. Connect one connector on one end of the power cable 1 to the backplane power connector on the
system board. Then, connect the two connectors on the other end of the power cable to the power
connectors on the hard-disk-drive backplane 1 and 2.
Figure 117. Hot-swap HDD cable connection: eight HDDs, ServeRAID SAS/SATA controller installed on the left side
Simple-swap HDD cable connection: ServeRAID SAS/SATA controller and redundant

power supply
• 2: Connect to the connector 0 on the ServeRAID SAS/SATA controller and the four connectors on the
hard-disk-drive backplate assembly.
Notes:
the system board.

Figure 118. Simple-swap HDD cable connection: four HDDs, ServeRAID SAS/SATA controller installed on the right side
Figure 119. Simple-swap HDD cable connection: four HDDs, ServeRAID SAS/SATA controller installed on the left side
To connect cables for the server models with eight simple-swap hard disk drives, do the following:

• 1: Connect to the backplane power connector on the system board.

• 3: Connect to the connector 0 on the ServeRAID SAS/SATA controller.
• 4: Connect to the power connector 2.
• 5: Connect to the connector 1 on the ServeRAID SAS/SATA controller.
Figure 121. Simple-swap HDD cable connection: eight HDDs, ServeRAID SAS/SATA controller installed on the left side
Completing the parts replacement

To complete the parts replacement, do the following:
Note: Ensure that all components have been reassembled properly and that no tools or loose screws are left
inside your server.
1. Properly route and secure the cables in the server. Refer to the cable connecting and routing information
for each component. See “Internal cable routing” on page 157.
2. If you removed the server cover, reinstall it. See “Installing the server cover” on page 95.
3. Install the server into the rack. See the Rack Installation Instructions that comes with the server.
4. Reconnect the power cords.
5. Update the server configuration.

a. Save the new configuration settings when starting the server for the first time after you add or remove
a device. The Setup Utility program starts automatically.
b. Install device drivers for some optional devices. See the documentation that comes with each device
c. Reconfigure the disk arrays if you have installed or removed an HDD and a RAID adapter. See the
documentation that comes with the RAID adapter.
d. Configure the Ethernet controller, see “Ethernet controller information” on page 38.
6. Start the server. Confirm that it starts properly and recognizes the newly installed devices, and make
sure that no error LEDs are lit.
7. For Business Partners only: Complete the additional steps in “Instructions for Business Partners” on
page 171.
Instructions for Business Partners

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

Before you send DSA data to Lenovo, read the terms of use at:
http://www.ibm.com/de/support/ ecurep/terms.html
You can use any of the following methods to send the DSA data to Lenovo:
• Standard upload:
http://www.ibm.com/de/support/ ecurep/send_http.html
• Standard upload with the system serial number:
http://www.ecurep.ibm.com/app/ upload_hw
• Secure upload:
http://www.ibm.com/de/support/ ecurep/send_http.html#secure
• Secure upload with the system serial number:
https://www.ecurep.ibm.com/ app/upload_hw
Returning a device or component

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

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

• Critical: A key component in the server is no longer functioning.
• Warning: The event might progress to a critical level.
• 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.
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.1 error messages and suggested actions to correct the detected server
problems. For more information about IMM2.1, see the Integrated Management Module II User's Guide at
http://publib.boulder.ibm.com/infocenter/systemx/documentation/topic/com.lenovo.sysx.imm2.doc/ product_
page.html.
IMM Events that automatically notify Support

You can configure the Integrated Management Module II (IMM2) to automatically notify Support (also known
as call home) if certain types of errors are encountered. If you have configured this function, see the table for
a list of events that automatically notify Support.
Table 29. Events that automatically notify Support
Automatically
Event ID Message String Notify Support
40000086-00000000 Test Call Home Generated by user [arg1]. Yes
40000087-00000000 Manual Call Home by user [arg1]: [arg2]. Yes
400000cb-00000000 The RAID controller has problem with the battery. Please Yes
contact technical support to resolve this issue.([arg1],
[arg2],[arg3],[arg4],[arg5])
400000cc-00000000 The RAID controller detected unrecoverable error. The Yes

controller needs replacement.([arg1],[arg2],[arg3],[arg4],
[arg5])
400000d5-00000000 One or more virtual drive have problem. Please contact Yes
technical support to resolve this issue.([arg1],[arg2],[arg3],
[arg4],[arg5])
400000d6-00000000 Drive error was detected by RAID controller. Please Yes

contact technical support to resolve this issue.([arg1],
[arg2],[arg3],[arg4],[arg5])
80010202-0701ffff Numeric sensor [NumericSensorElementName] going low Yes

(lower critical) has asserted. (CMOS Battery)
80010902-0701ffff Numeric sensor [NumericSensorElementName] going Yes

high (upper critical) has asserted. (SysBrd 12V)

Table 29. Events that automatically notify Support (continued)
Automatically
806f0021-2201ffff Fault in slot [PhysicalConnectorSystemElementName] on Yes

system [ComputerSystemElementName]. (No Op ROM
Space)

system [ComputerSystemElementName]. (All PCI Error)

system [ComputerSystemElementName]. (PCI 1)

system [ComputerSystemElementName]. (PCI 2)
806f0108-0a01ffff [PowerSupplyElementName] has Failed. (Power Supply 1) Yes
806f0108-0a02ffff [PowerSupplyElementName] has Failed. (Power Supply 2) Yes
806f010c-2001ffff Uncorrectable error detected for Yes

[PhysicalMemoryElementName] on Subsystem
[MemoryElementName]. (DIMM 1)




[MemoryElementName]. (All DIMMS)
806f010d-0400ffff The Drive [StorageVolumeElementName] has been Yes

disabled due to a detected fault. (Drive 0)







Appendix A. Integrated Management Module 2.1 (IMM2.1) error messages 175

Automatically

disabled due to a detected fault. (Ext Drive)
806f0207-0301ffff [ProcessorElementName] has Failed with FRB1/BIST Yes

condition. (CPU 1)
806f020d-0400ffff Failure Predicted on drive [StorageVolumeElementName] Yes

for array [ComputerSystemElementName]. (Drive 0)








for array [ComputerSystemElementName]. (Ext Drive)
806f050c-2001ffff Memory Logging Limit Reached for Yes





806f060d-0400ffff Array [ComputerSystemElementName] has failed. (Drive Yes

0)

1)

2)

Automatically

3)

4)

5)

6)

7)
806f060d-0410ffff Array [ComputerSystemElementName] has failed. (Ext Yes

Drive)
806f0813-2582ffff An Uncorrectable Bus Error has occurred on system Yes

[ComputerSystemElementName]. (PCIs)
806f0813-2584ffff An Uncorrectable Bus Error has occurred on system Yes

[ComputerSystemElementName]. (CPUs)
List of IMM events

This section lists all messages that can be sent from the IMM.
• 40000001-00000000 : Management Controller [arg1] Network Initialization Complete.

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
Serviceable
No
Automatically notify support
No
Alert Category
System - IMM Network event
SNMP Trap ID
37
CIM Information
Prefix: IMM ID: 0001
User Response
Information only; no action is required.
• 40000002-00000000 : Certificate Authority [arg1] has detected a [arg2] Certificate Error.
This message is for the use case when there is an error with an SSL Server, SSL Client, or SSL Trusted CA
Certificate.

Severity
Error
Serviceable
No
No
Alert Category
System - SSL certification
SNMP Trap ID
22
CIM Information
User Response
Make sure that the certificate that you are importing is correct and properly generated.
• 40000003-00000000 : Ethernet Data Rate modified from [arg1] to [arg2] by user [arg3].
This message is for the use case where a user modifies the Ethernet Port data rate.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000004-00000000 : Ethernet Duplex setting modified from [arg1] to [arg2] by user [arg3].
This message is for the use case where A user modifies the Ethernet Port duplex setting.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID

CIM Information
User Response
• 40000005-00000000 : Ethernet MTU setting modified from [arg1] to [arg2] by user [arg3].
This message is for the use case where a user modifies the Ethernet Port MTU setting.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000006-00000000 : Ethernet locally administered MAC address modified from [arg1] to [arg2] by
user [arg3].
This message is for the use case where a user modifies the Ethernet Port MAC address setting.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000007-00000000 : Ethernet interface [arg1] by user [arg2].
This message is for the use case where a user enables or disabled the ethernet interface.
Severity

Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000008-00000000 : Hostname set to [arg1] by user [arg2].
This message is for the use case where user modifies the Hostname of a Management Controller.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
37
CIM Information
User Response
• 40000009-00000000 : IP address of network interface modified from [arg1] to [arg2] by user [arg3].
This message is for the use case where user modifies the IP address of a Management Controller.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
37

CIM Information
User Response
• 4000000a-00000000 : IP subnet mask of network interface modified from [arg1] to [arg2] by user
[arg3].
This message is for the use case where a user modifies the IP subnet mask of a Management Controller.
May also be shown as 4000000a00000000 or 0x4000000a00000000
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000000b-00000000 : IP address of default gateway modified from [arg1] to [arg2] by user [arg3].
This message is for the use case where a user modifies the default gateway IP address of a Management
Controller.
May also be shown as 4000000b00000000 or 0x4000000b00000000
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000000c-00000000 : OS Watchdog response [arg1] by [arg2].
This message is for the use case where an OS Watchdog has been enabled or disabled by a user.
May also be shown as 4000000c00000000 or 0x4000000c00000000

Severity
Warning
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000000d-00000000 : DHCP[[arg1]] failure, no IP address assigned.
This message is for the use case where a DHCP server fails to assign an IP address to a Management
Controller.
May also be shown as 4000000d00000000 or 0x4000000d00000000
Severity
Warning
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
Complete the following steps until the problem is solved:
1. Make sure that the IMM network cable is connected.
2. Make sure that there is a DHCP server on the network that can assign an IP address to the IMM.
• 4000000e-00000000 : Remote Login Successful. Login ID: [arg1] from [arg2] at IP address [arg3].
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
Serviceable
No
No

Alert Category
System - Remote Login
SNMP Trap ID
30
CIM Information
User Response
• 4000000f-00000000 : Attempting to [arg1] server [arg2] by user [arg3].
This message is for the use case where a user is using the Management Controller to perform a power
function on the system.
May also be shown as 4000000f00000000 or 0x4000000f00000000
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000010-00000000 : Security: Userid: [arg1] had [arg2] login failures from WEB client at IP address
[arg3].
This message is for the use case where a user has failed to log in to a Management Controller from a web
browser.
Severity
Warning
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response

1. Make sure that the correct login ID and password are being used.
2. Have the system administrator reset the login ID or password.
• 40000011-00000000 : Security: Login ID: [arg1] had [arg2] login failures from CLI at [arg3].
This message is for the use case where a user has failed to log in to a Management Controller from the
Legacy CLI.
Severity
Warning
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 40000012-00000000 : Remote access attempt failed. Invalid userid or password received. Userid is
[arg1] from WEB browser at IP address [arg2].
This message is for the use case where a remote user has failed to establish a remote control session
from a Web browser session.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
Make sure that the correct login ID and password are being used.
• 40000013-00000000 : Remote access attempt failed. Invalid userid or password received. Userid is
[arg1] from TELNET client at IP address [arg2].

This message is for the use case where a user has failed to log in to a Management Controller from a
telnet session.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
Make sure that the correct login ID and password are being used.
• 40000014-00000000 : The [arg1] on system [arg2] cleared by user [arg3].
This message is for the use case where a Management Controller Event Log on a system is cleared by a
user.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000015-00000000 : Management Controller [arg1] reset was initiated by user [arg2].
This message is for the use case where a Management Controller reset is initiated by a user.
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000016-00000000 : ENET[[arg1]] DHCP-HSTN=[arg2], DN=[arg3], IP@=[arg4], SN=[arg5], GW@=
[arg6], DNS1@=[arg7].
This message is for the use case where a Management Controller IP address and configuration has been
assigned by the DHCP server.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000017-00000000 : ENET[[arg1]] IP-Cfg:HstName=[arg2], IP@=[arg3] ,NetMsk=[arg4], GW@=
[arg5].
This message is for the use case where a Management Controller IP address and configuration has been
assigned statically using user data.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information

User Response
• 40000018-00000000 : LAN: Ethernet[[arg1]] interface is no longer active.
This message is for the use case where a Management Controller ethernet interface is no longer active.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000019-00000000 : LAN: Ethernet[[arg1]] interface is now active.
This message is for the use case where a Management Controller ethernet interface is now active.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000001a-00000000 : DHCP setting changed to [arg1] by user [arg2].
This message is for the use case where a user changes the DHCP setting.
Severity
Info
Serviceable

No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000001b-00000000 : Management Controller [arg1]: Configuration restored from a file by user
[arg2].
This message is for the use case where a user restores a Management Controller configuration from a file.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000001c-00000000 : Watchdog [arg1] Screen Capture Occurred.
This message is for the use case where an operating system error has occurred and the screen was
captured.
Severity
Info
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information

User Response
If there was no operating-system error, complete the following steps until the problem is solved:
1. Reconfigure the watchdog timer to a higher value.
2. Make sure that the IMM Ethernet-over-USB interface is enabled.
3. Reinstall the RNDIS or cdc_ether device driver for the operating system.
4. Disable the watchdog.
If there was an operating-system error, check the integrity of the installed operating system.
• 4000001d-00000000 : Watchdog [arg1] Failed to Capture Screen.
This message is for the use case where an operating system error has occurred and the screen capture
failed.
Severity
Error
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information
User Response
2. Make sure that the IMM Ethernet over USB interface is enabled.
4. Disable the watchdog. Check the integrity of the installed operating system.
5. Update the IMM firmware. Important: Some cluster solutions require specific code levels or
coordinated code updates. If the device is part of a cluster solution, verify that the latest level of
code is supported for the cluster solution before you update the code.
• 4000001e-00000000 : Running the backup Management Controller [arg1] main application.
This message is for the use case where a Management Controller has resorted to running the backup
main application.
Severity
Warning
Serviceable
No
No

Alert Category
System - other
SNMP Trap ID
22
CIM Information
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.
This message is for the use case where a Management Controller firmware version does not match the
server.
Severity
Error
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information
User Response
Update the IMM firmware to a version that the server supports. Important: Some cluster solutions
require specific code levels or coordinated code updates. If the device is part of a cluster solution,
verify that the latest level of code is supported for the cluster solution before you update the code.
• 40000020-00000000 : Management Controller [arg1] Reset was caused by restoring default values.
This message is for the use case where a Management Controller has been reset due to a user restoring
the configuration to default values.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID

CIM Information
User Response
• 40000021-00000000 : Management Controller [arg1] clock has been set from NTP server [arg2].
This message is for the use case where a Management Controller clock has been set from the Network
Time Protocol server.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000022-00000000 : SSL data in the Management Controller [arg1] configuruation data is invalid.
Clearing configuration data region and disabling SSL.
This message is for the use case where a Management Controller has detected invalid SSL data in the
configuration data and is clearing the configuration data region and disabling the SSL.
Severity
Error
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information
User Response
1. Make sure that the certificate that you are importing is correct.
2. Try to import the certificate again.
• 40000023-00000000 : Flash of [arg1] from [arg2] succeeded for user [arg3].

This message is for the use case where a user has successfully flashed the firmware component (MC Main
Application, MC Boot ROM, BIOS, Diagnostics, System Power Backplane, Remote Expansion Enclosure
Power Backplane, Integrated System Management Processor, or Remote Expansion Enclosure
Processor) from the interface and IP address ( %d.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000024-00000000 : Flash of [arg1] from [arg2] failed for user [arg3].
This message is for the use case where a user has not flashed the firmware component from the interface
and IP address due to a failure.
Severity
Info
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information
User Response
• 40000025-00000000 : The [arg1] on system [arg2] is 75% full.
This message is for the use case where a Management Controller Event Log on a system is 75% full.
Severity
Info
Serviceable
No

No
Alert Category
System - Event Log 75% full
SNMP Trap ID
35
CIM Information
User Response
• 40000026-00000000 : The [arg1] on system [arg2] is 100% full.
This message is for the use case where a Management Controller Event Log on a system is 100% full.
Severity
Info
Serviceable
No
No
Alert Category
System - Event Log Fullness
SNMP Trap ID
35
CIM Information
User Response
To avoid losing older log entries, save the log as a text file and clear the log.
• 40000027-00000000 : Platform Watchdog Timer expired for [arg1].
This message is for the use case when an implementation has detected a Platform Watchdog Timer
Expired
Severity
Error
Serviceable
No
No
Alert Category
System - OS Timeout
SNMP Trap ID
21
CIM Information

User Response
2. Make sure that the IMM Ethernet-over-USB interface is enabled.
5. Check the integrity of the installed operating system.
• 40000028-00000000 : Management Controller Test Alert Generated by [arg1].
This message is for the use case where a user has generated a Test Alert.
Severity
Info
Serviceable
No
No
Alert Category
System - other
SNMP Trap ID
22
CIM Information
User Response
• 40000029-00000000 : Security: Userid: [arg1] had [arg2] login failures from an SSH client at IP
address [arg3].
This message is for the use case where a user has failed to log in to a Management Controller from SSH.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response

• 4000002a-00000000 : [arg1] firmware mismatch internal to system [arg2]. Please attempt to flash
the [arg3] firmware.
This message is for the use case where a specific type of firmware mismatch has been detected.
Severity
Error
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Reflash the IMM firmware to the latest version.
• 4000002b-00000000 : Domain name set to [arg1].
Domain name set by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000002c-00000000 : Domain Source changed to [arg1] by user [arg2].
Domain source changed by user
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000002d-00000000 : DDNS setting changed to [arg1] by user [arg2].
DDNS setting changed by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000002e-00000000 : DDNS registration successful. The domain name is [arg1].
DDNS registation and values
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 4000002f-00000000 : IPv6 enabled by user [arg1].
IPv6 protocol is enabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000030-00000000 : IPv6 disabled by user [arg1].
IPv6 protocol is disabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000031-00000000 : IPv6 static IP configuration enabled by user [arg1].
IPv6 static address assignment method is enabled by user
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000032-00000000 : IPv6 DHCP enabled by user [arg1].
IPv6 DHCP assignment method is enabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000033-00000000 : IPv6 stateless auto-configuration enabled by user [arg1].
IPv6 statless auto-assignment method is enabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 40000034-00000000 : IPv6 static IP configuration disabled by user [arg1].
IPv6 static assignment method is disabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000035-00000000 : IPv6 DHCP disabled by user [arg1].
IPv6 DHCP assignment method is disabled by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000036-00000000 : IPv6 stateless auto-configuration disabled by user [arg1].
IPv6 statless auto-assignment method is disabled by user
Severity
Info
Serviceable
No
No

Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000037-00000000 : ENET[[arg1]] IPv6-LinkLocal:HstName=[arg2], IP@=[arg3] ,Pref=[arg4].
IPv6 Link Local address is active
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000038-00000000 : ENET[[arg1]] IPv6-Static:HstName=[arg2], IP@=[arg3] ,Pref=[arg4], GW@=
[arg5].
IPv6 Static address is active
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000039-00000000 : ENET[[arg1]] DHCPv6-HSTN=[arg2], DN=[arg3], IP@=[arg4], Pref=[arg5].

IPv6 DHCP-assigned address is active
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000003a-00000000 : IPv6 static address of network interface modified from [arg1] to [arg2] by
user [arg3].
A user modifies the IPv6 static address of a Management Controller
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000003b-00000000 : DHCPv6 failure, no IP address assigned.
S DHCP6 server fails to assign an IP address to a Management Controller.
Severity
Warning
Serviceable
No
No

Alert Category
none
SNMP Trap ID
CIM Information
User Response
1. Make sure that the IMM network cable is connected.
2. Make sure that there is a DHCPv6 server on the network that can assign an IP address to the
IMM.
• 4000003c-00000000 : Platform Watchdog Timer expired for [arg1].
An implementation has detected an OS Loader Watchdog Timer Expired
Severity
Error
Serviceable
No
No
Alert Category
System - Loader timeout
SNMP Trap ID
26
CIM Information
User Response
2. Make sure that the IMM Ethernet over USB interface is enabled.
5. Check the integrity of the installed operating system.
• 4000003d-00000000 : Telnet port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the telnet port number
Severity
Info
Serviceable
No
No
Alert Category
none

SNMP Trap ID
CIM Information
User Response
• 4000003e-00000000 : SSH port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the SSH port number
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000003f-00000000 : Web-HTTP port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the Web HTTP port number
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000040-00000000 : Web-HTTPS port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the Web HTTPS port number

Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000041-00000000 : CIM/XML HTTP port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the CIM HTTP port number
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000042-00000000 : CIM/XML HTTPS port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the CIM HTTPS port number
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID

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

Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000046-00000000 : Remote Presence port number changed from [arg1] to [arg2] by user [arg3].
A user has modified the Remote Presence port number
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000047-00000000 : LED [arg1] state changed to [arg2] by [arg3].
A user has modified the state of an LED
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information

User Response
• 40000048-00000000 : Inventory data changed for device [arg1], new device data hash=[arg2], new
master data hash=[arg3].
Something has caused the physical inventory to change
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000049-00000000 : SNMP [arg1] enabled by user [arg2].
A user enabled SNMPv1 or SNMPv3 or Traps
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000004a-00000000 : SNMP [arg1] disabled by user [arg2].
A user disabled SNMPv1 or SNMPv3 or Traps
Severity
Info
Serviceable

No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000004b-00000000 : SNMPv1 [arg1] set by user [arg2]: Name=[arg3], AccessType=[arg4],
Address=[arg5].
A user changed the SNMP community string
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000004c-00000000 : LDAP Server configuration set by user [arg1]: SelectionMethod=[arg2],
DomainName=[arg3], Server1=[arg4], Server2=[arg5], Server3=[arg6], Server4=[arg7].
A user changed the LDAP server configuration
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information

User Response
• 4000004d-00000000 : LDAP set by user [arg1]: RootDN=[arg2], UIDSearchAttribute=[arg3],
BindingMethod=[arg4], EnhancedRBS=[arg5], TargetName=[arg6], GroupFilter=[arg7],
GroupAttribute=[arg8], LoginAttribute=[arg9].
A user configured an LDAP Miscellaneous setting
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000004e-00000000 : Serial Redirection set by user [arg1]: Mode=[arg2], BaudRate=[arg3],
StopBits=[arg4], Parity=[arg5], SessionTerminateSequence=[arg6].
A user configured the Serial Port mode
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000004f-00000000 : Date and Time set by user [arg1]: Date=[arg2], Time-[arg3], DST Auto-adjust=
[arg4], Timezone=[arg5].
A user configured the Date and Time settings

Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000050-00000000 : Server General Settings set by user [arg1]: Name=[arg2], Contact=[arg3],
Location=[arg4], Room=[arg5], RackID=[arg6], Rack U-position=[arg7].
A user configured the Location setting
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000051-00000000 : Server Power Off Delay set to [arg1] by user [arg2].
A user configured the Server Power Off Delay
Severity
Info
Serviceable
No
No
Alert Category
none

SNMP Trap ID
CIM Information
User Response
• 40000052-00000000 : Server [arg1] scheduled for [arg2] at [arg3] by user [arg4].
A user configured a Server Power action at a specific time
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000053-00000000 : Server [arg1] scheduled for every [arg2] at [arg3] by user [arg4].
A user configured a recurring Server Power Action
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000054-00000000 : Server [arg1] [arg2] cleared by user [arg3].
A user cleared a Server Power Action.

Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000055-00000000 : Synchronize time setting by user [arg1]: Mode=[arg2], NTPServerHost1=
[arg3]:[arg4], NTPServerHost2=[arg5]:[arg6], NTPServerHost3=[arg7]:[arg8], NTPServerHost4=
[arg9]:[arg10], NTPUpdateFrequency=[arg11].
A user configured the Date and Time synchronize settings
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000056-00000000 : SMTP Server set by user [arg1] to [arg2]:[arg3].
A user configured the SMTP server
Severity
Info
Serviceable
No
No
Alert Category
none

SNMP Trap ID
CIM Information
User Response
• 40000057-00000000 : Telnet [arg1] by user [arg2].
A user enables or disables Telnet services
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000058-00000000 : DNS servers set by user [arg1]: UseAdditionalServers=[arg2],
PreferredDNStype=[arg3], IPv4Server1=[arg4], IPv4Server2=[arg5], IPv4Server3=[arg6],
IPv6Server1=[arg7], IPv6Server2=[arg8], IPv6Server3=[arg9].
A user configures the DNS servers
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000059-00000000 : LAN over USB [arg1] by user [arg2].
A user configured USB-LAN

Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000005a-00000000 : LAN over USB Port Forwarding set by user [arg1]: ExternalPort=[arg2], USB-
LAN port=[arg3].
A user configured USB-LAN port forwarding
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000005b-00000000 : Secure Web services (HTTPS) [arg1] by user [arg2].
A user enables or disables Secure web services
Severity
Info
Serviceable
No
No
Alert Category

none
SNMP Trap ID
CIM Information
User Response
• 4000005c-00000000 : Secure CIM/XML(HTTPS) [arg1] by user [arg2].
A user enables or disables Secure CIM/XML services
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000005d-00000000 : Secure LDAP [arg1] by user [arg2].
A user enables or disables Secure LDAP services
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000005e-00000000 : SSH [arg1] by user [arg2].
A user enables or disables SSH services

Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000005f-00000000 : Server timeouts set by user [arg1]: EnableOSWatchdog=[arg2],
OSWatchdogTimout=[arg3], EnableLoaderWatchdog=[arg4], LoaderTimeout=[arg5].
A user configures Server Timeouts
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000060-00000000 : License key for [arg1] added by user [arg2].
A user installs License Key
Severity
Info
Serviceable
No
No
Alert Category

none
SNMP Trap ID
CIM Information
User Response
• 40000061-00000000 : License key for [arg1] removed by user [arg2].
A user removes a License Key
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000062-00000000 : Global Login General Settings set by user [arg1]: AuthenticationMethod=
[arg2], LockoutPeriod=[arg3], SessionTimeout=[arg4].
A user changes the Global Login General Settings
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 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].
A user changes the Global Login Account Security Settings to Legacy
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000064-00000000 : User [arg1] created.
A user account was created
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000065-00000000 : User [arg1] removed.
A user account was deleted
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000066-00000000 : User [arg1] password modified.
A user account was changed
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000067-00000000 : User [arg1] role set to [arg2].
A user account role assigned
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 40000068-00000000 : User [arg1] custom privileges set: [arg2].
User account priveleges assigned
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000069-00000000 : User [arg1] for SNMPv3 set: AuthenticationProtocol=[arg2], PrivacyProtocol=
[arg3], AccessType=[arg4], HostforTraps=[arg5].
User account SNMPv3 settings changed
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000006a-00000000 : SSH Client key added for user [arg1].
User locally defined an SSH Client key
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000006b-00000000 : SSH Client key imported for user [arg1] from [arg2].
User imported an SSH Client key
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000006c-00000000 : SSH Client key removed from user [arg1].
User removed an SSH Client key
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 4000006d-00000000 : Management Controller [arg1]: Configuration saved to a file by user [arg2].
A user saves a Management Controller configuration to a file.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000006e-00000000 : Alert Configuration Global Event Notification set by user [arg1]: RetryLimit=
[arg2], RetryInterval=[arg3], EntryInterval=[arg4].
A user changes the Global Event Notification settings.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000006f-00000000 : Alert Recipient Number [arg1] updated: Name=[arg2], DeliveryMethod=[arg3],
Address=[arg4], IncludeLog=[arg5], Enabled=[arg6], EnabledAlerts=[arg7], AllowedFilters=[arg8].
A user adds or updates an Alert Recipient
Severity
Info
Serviceable

No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000070-00000000 : SNMP Traps enabled by user [arg1]: EnabledAlerts=[arg2], AllowedFilters=
[arg3].
A user enabled the SNMP Traps configuration
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000071-00000000 : The power cap value changed from [arg1] watts to [arg2] watts by user
[arg3].
Power Cap values changed by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information

User Response
• 40000072-00000000 : The minimum power cap value changed from [arg1] watts to [arg2] watts.
Minimum Power Cap value changed
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000073-00000000 : The maximum power cap value changed from [arg1] watts to [arg2] watts.
Maximum Power Cap value changed
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000074-00000000 : The soft minimum power cap value changed from [arg1] watts to [arg2]
watts.
Soft Minimum Power Cap value changed
Severity
Info

Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000075-00000000 : The measured power value exceeded the power cap value.
Power exceeded cap
Severity
Warning
Serviceable
No
No
Alert Category
Warning - Power
SNMP Trap ID
164
CIM Information
User Response
• 40000076-00000000 : The new minimum power cap value exceeded the power cap value.
Minimum Power Cap exceeds Power Cap
Severity
Warning
Serviceable
No
No
Alert Category
Warning - Power
SNMP Trap ID
164
CIM Information

User Response
• 40000077-00000000 : Power capping was activated by user [arg1].
Power capping activated by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000078-00000000 : Power capping was deactivated by user [arg1].
Power capping deactivated by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000079-00000000 : Static Power Savings mode has been turned on by user [arg1].
Static Power Savings mode turned on by user
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000007a-00000000 : Static Power Savings mode has been turned off by user [arg1].
Static Power Savings mode turned off by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000007b-00000000 : Dynamic Power Savings mode has been turned on by user [arg1].
Dynamic Power Savings mode turned on by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 4000007c-00000000 : Dynamic Power Savings mode has been turned off by user [arg1].
Dynamic Power Savings mode turned off by user
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000007d-00000000 : Power cap and external throttling occurred.
Power cap and external throttling occurred
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000007e-00000000 : External throttling occurred.
External throttling occurred
Severity
Info
Serviceable
No

No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 4000007f-00000000 : Power cap throttling occurred.
Power cap throttling occurrred
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000080-00000000 : Remote Control session started by user [arg1] in [arg2] mode.
Remote Control session started
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response

• 40000081-00000000 : PXE boot requested by user [arg1].
PXE boot requested
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000082-00000000 : The measured power value has returned below the power cap value.
Power exceeded cap recovered
Severity
Info
Serviceable
No
No
Alert Category
Warning - Power
SNMP Trap ID
164
CIM Information
User Response
• 40000083-00000000 : The new minimum power cap value has returned below the power cap value.
Minimum Power Cap exceeds Power Cap recovered
Severity
Info
Serviceable
No
No

Alert Category
Warning - Power
SNMP Trap ID
164
CIM Information
User Response
• 40000084-00000000 : IMM firmware mismatch between nodes [arg1] and [arg2]. Please attempt to
flash the IMM firmware to the same level on all nodes.
A mismatch of IMM firmware has been detected between nodes
Severity
Error
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
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.
A mismatch of FPGA firmware has been detected between nodes
Severity
Error
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Attempt to flash the FPGA firmware to the same level on all nodes.

• 40000086-00000000 : Test Call Home Generated by user [arg1].
Test Call Home generated by user.
Severity
Info
Serviceable
No
Yes
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000087-00000000 : Manual Call Home by user [arg1]: [arg2].
Manual Call Home by user.
Severity
Info
Serviceable
No
Yes
Alert Category
none
SNMP Trap ID
CIM Information
User Response
Lenovo Support will address the problem.
• 40000088-00000000 : Management Controller [arg1]: Configuration restoration from a file by user
[arg2] completed.
This message is for the use case where a user restores a Management Controller configuration from a file
and it completes.
Severity
Info
Serviceable
No

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

System - Other
SNMP Trap ID
22
CIM Information
User Response
1. Turn off the server and disconnect it from the power source. You must disconnect the server
from ac power to reset the IMM.
2. After 45 seconds, reconnect the server to the power source and turn on the server.
3. Retry the operation.
• 4000008b-00000000 : Storage [arg1] has changed.
This message is for the use case where an IP address for the Storage Management has changed
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
37
CIM Information
User Response
• 4000008c-00000000 : Security: Userid: [arg1] had [arg2] login failures from a CIM client at IP
address [arg3].
This message is for the use case where a user has failed to log in to a Management Controller from CIM.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information

User Response
• 4000008d-00000000 : Remote access attempt failed. Invalid userid or password received. Userid is
[arg1] from a CIM client at IP address [arg2].
This message is for the use case where a remote user has failed to establish a remote control session
from CIM.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000008e-00000000 : Device [arg1] VPD is not valid.
The VPD for a device is invalid
Severity
Warning
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 4000008f-00000000 : The bare metal connection process has been started.
Bare Metal Connection process has been started
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 40000090-00000000 : The bare metal update application reports a status of [arg1].
Bare Metal Update Application Status
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 40000091-00000000 : User [arg1] has terminated an active console session.
A user has terminated an active console session
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information

User Response
• 40000092-00000000 : TKLM servers set by user [arg1]: TKLMServer1=[arg2] Port=[arg3],
TKLMServer2=[arg4] Port=[arg5], TKLMServer3=[arg6] Port=[arg7], TKLMServer4=[arg8] Port=
[arg9].
A user configured the TKLM servers
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000093-00000000 : TKLM servers device group set by user [arg1]: TKLMServerDeviceGroup=
[arg2].
A user configured the TKLM device group
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000094-00000000 : User [arg1] has generated a new encryption key pair and installed a self-
signed certificate for the TKLM client.
User generated a new encryption key pair and installed a self-signed certificate for the TKLM client
Severity

Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000095-00000000 : User [arg1] has generated a new encryption key and certificate signing
request for the TKLM client.
User generated a new encryption key and certificate signing request for the TKLM client
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000096-00000000 : User [arg1] has imported a signed certificate for the TKLM client from [arg2].
User imported a signed certificate for the TKLM client
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID

CIM Information
User Response
• 40000097-00000000 : User [arg1] has imported a server certificate for the TKLM server.
User imported a server certificate for the TKLM Server
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000098-00000000 : The UEFI Definitions have been changed.
UEFI Definitions change has been detected
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 40000099-00000000 : Security: Userid: [arg1] had [arg2] login failures from IPMI client at IP address
[arg3].
This message is for the use case where a user has failed to log in to a Management Controller from IPMI.
Severity

Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000009a-00000000 : Security: Userid: [arg1] had [arg2] login failures from SNMP client at IP
address [arg3].
This message is for the use case where a user has failed to access a Management Controller from SNMP.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000009b-00000000 : Security: Userid: [arg1] had [arg2] login failures from IPMI serial client.
This message is for the use case where a user has failed to log in to a Management Controller from IPMI
serial client
Severity
Info
Serviceable
No
No
Alert Category

SNMP Trap ID
30
CIM Information
User Response
• 4000009c-00000000 : Remote Login Successful. Login ID: [arg1] from [arg2] serial interface.
This message is for the use case where a user successfully logs in to a Management Controller.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000009d-00000000 : Login ID: [arg1] from [arg2] at IP address [arg3] has logged off.
This message is for the use case where a user has logged off of a Management Controller.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000009e-00000000 : Login ID: [arg1] from [arg2] at IP address [arg3] has been logged off.
This message is for the use case where a user has been logged off of a Management Controller.

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
30
CIM Information
User Response
• 4000009f-00000000 : User [arg1] has initiated a TKLM Server Connection Test to check
connectivity to server [arg2].
User initiated a TKLM Server Connection test.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 400000a0-00000000 : User [arg1] has initiated an SMTP Server Connection Test.
User initiated an SMTP Server Connection test.
Severity
Info
Serviceable
No
No
Alert Category
none

SNMP Trap ID
CIM Information
User Response
• 400000a1-00000000 : UEFI Reported: [arg1].
UEFI audit event logged.
Severity
Info
Serviceable
No
No
Alert Category
none
SNMP Trap ID
CIM Information
User Response
• 400000a2-00000000 : User [arg1] has [arg2] file [arg3] from [arg4].
User has mounted/unmounted file from URL or server
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a3-00000000 : User [arg1] has set the SMTP Server reverse-path to [arg2].
User set SMTP Server reverse-path address

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a4-00000000 : User [arg1] has removed a certificate.
User removed certificate
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a5-00000000 : A certificate has been revoked.
A certificate has been revoked
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22

CIM Information
User Response
• 400000a6-00000000 : The server was restarted for an unknown reason.
The server was restarted for an unknown reason
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a7-00000000 : The server is restarted by chassis control command.
Server is restarted by chassis control command
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a8-00000000 : The server was reset via pushbutton.
Server was reset via pushbutton
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000a9-00000000 : The server was powered-up via power pushbutton.
Server was power-up via power pushbutton
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000aa-00000000 : The server was restarted when the watchdog expired..
Server was restarted when the watchdog expired.
May also be shown as 400000aa00000000 or 0x400000aa00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
• 400000ab-00000000 : The server was restarted for OEM reason.
Server was restarted for OEM reason
May also be shown as 400000ab00000000 or 0x400000ab00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000ac-00000000 : The server was automatically powered on because the power restore policy
is set to always restore..
Server was automatically powered on because the power restore policy is set to always restore.
May also be shown as 400000ac00000000 or 0x400000ac00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000ad-00000000 : The server was automatically powered on because the power restore policy
is set to restore previous power state..
Server was automatically powered on because the power restore policy is set to restore previous power
state.
May also be shown as 400000ad00000000 or 0x400000ad00000000
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000ae-00000000 : The server was reset via Platform Event Filter.
Server was reset via Platform Event Filter
May also be shown as 400000ae00000000 or 0x400000ae00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000af-00000000 : The server was power-cycled via Platform Event Filter.
Server was power-cycled via Platform Event Filter
May also be shown as 400000af00000000 or 0x400000af00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
• 400000b0-00000000 : The server was soft reset.
Server was soft reset
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b1-00000000 : The server was powered up via Real Time Clock (scheduled power on).
Server was powered up via Real Time Clock (scheduled power on)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b2-00000000 : The server was powered off for an unknown reason.
Server was powered off for an unknown reason
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b3-00000000 : The server was powered off by chassis control command.
Server was powered off by chassis control command
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b4-00000000 : The server was powered off via pushbutton.
Server was powered off via pushbutton
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response

• 400000b5-00000000 : The server was powered off when the watchdog expired.
Server was powered off when the watchdog expired.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b6-00000000 : The server stayed powered off because the power restore policy is set to
always restore..
Server stayed powered off because the power restore policy is set to always restore.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b7-00000000 : The server stayed powered off because the power restore policy is set to
restore previous power state..
Server stayed powered off because the power restore policy is set to restore previous power state.
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b8-00000000 : The server was popwered off via Platform Event Filter.
Server was power off via Platform Event Filter
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000b9-00000000 : The server was powered off via Real Time Clock (scheduled power off).
Server was powered up via Real Time Clock (scheduled power off)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
• 400000ba-00000000 : Management Controller [arg1] reset was initiated due to Power-On-Reset.
Management Controller reset was initiated due to Power-On-Reset
May also be shown as 400000ba00000000 or 0x400000ba00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000bb-00000000 : Management Controller [arg1] reset was initiated by PRESET.
Management Controller reset was initiated by PRESET
May also be shown as 400000bb00000000 or 0x400000bb00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000bc-00000000 : Management Controller [arg1] reset was initiated by CMM.
Management Controller reset was initiated by CMM
May also be shown as 400000bc00000000 or 0x400000bc00000000
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000bd-00000000 : Management Controller [arg1] reset was initiated by IMM firmware.
Management Controller reset was initiated by IMM firmware
May also be shown as 400000bd00000000 or 0x400000bd00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000be-00000000 : The [arg1] certificate is expired and has been removed.
Expired certificate has been removed
May also be shown as 400000be00000000 or 0x400000be00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response

• 400000bf-00000000 : Operating System status has changed to [arg1].
Operating System status change
May also be shown as 400000bf00000000 or 0x400000bf00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c1-00000000 : System running in setup.
System running in setup
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c2-00000000 : Remote Control session started by user [arg1] in [arg2] mode has been
closed.
Remote Control session closed
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c3-00000000 : Call Home to [arg1] failed to complete: [arg2].
Call Home failed to complete.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c4-00000000 : IMM failed to log previous event [arg1].
IMM failed to log a previous event.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response

• 400000c5-00000000 : UEFI deployment boot mode is enabled for NextBoot.
UEFI deployment boot mode is enabled for NextBoot
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c6-00000000 : UEFI deployment boot mode is enabled for NextAc.
UEFI deployment boot mode is enabled for NextAC
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c7-00000000 : UEFI deployment boot mode has been disabled.
UEFI deployment boot mode has been disabled
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000c9-00000000 : User [arg1] made system [arg2] Encapsulation lite Mode.
Encapsulation lite mode status change
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000ca-00000000 : Battery error was detected by RAID controller. The battery unit needs
replacement.([arg1],[arg2],[arg3],[arg4],[arg5])
Battery error was detected by RAID controller
May also be shown as 400000ca00000000 or 0x400000ca00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response

Check storage documentation by LSI Event ID.
• 400000cb-00000000 : The RAID controller has problem with the battery. Please contact technical
support to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
The RAID controller has problem with the battery
May also be shown as 400000cb00000000 or 0x400000cb00000000
Severity
Info
Serviceable
No
Yes
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000cc-00000000 : The RAID controller detected unrecoverable error. The controller needs
replacement.([arg1],[arg2],[arg3],[arg4],[arg5])
The RAID controller detected unrecoverable error
May also be shown as 400000cc00000000 or 0x400000cc00000000
Severity
Info
Serviceable
No
Yes
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000cd-00000000 : The RAID controller detected one or more problems. Please contact
technical support for additional assistance.([arg1],[arg2],[arg3],[arg4],[arg5])
The RAID controller detected one or more problems
May also be shown as 400000cd00000000 or 0x400000cd00000000
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000ce-00000000 : The RAID controller detected one or more possible configuration changes
within the subsystem. Please check the drive LED status. If necessary, contact technical support
for additional assistance.([arg1],[arg2],[arg3],[arg4],[arg5])
The RAID controller detected one or more possible configuration changes within the subsystem
May also be shown as 400000ce00000000 or 0x400000ce00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000cf-00000000 : Enclosure issue detected with one or more units. Please check the enclosure
units to repair the problem.([arg1],[arg2],[arg3],[arg4],[arg5])
Enclosure issue detected with one or more units
May also be shown as 400000cf00000000 or 0x400000cf00000000
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

22
CIM Information
User Response
• 400000d0-00000000 : Connectivity issue detected with the enclosure. Please check your cable
configurations to repair the problem.([arg1],[arg2],[arg3],[arg4],[arg5])
Connectivity issue detected with the enclosure
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d1-00000000 : Fan problem detected with the enclosure. Please check the enclosure unit
fan for correct operation.([arg1],[arg2],[arg3],[arg4],[arg5])
Fan problem detected with the enclosure
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d2-00000000 : Enclosure power supply has problem. Please check the enclosure unit power
supply for correct operation.([arg1],[arg2],[arg3],[arg4],[arg5])
Enclosure power supply has problem

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d3-00000000 : One or more virtual drive are in abnormal status that may cause unavailable
virtual drive. Please check the event logs and if events are targeted to the same disk then replace
the drive. If necessary, contact technical support for additional assistance.([arg1],[arg2],[arg3],
[arg4],[arg5])
One or more virtual drive are in abnormal status that may cause unavailable virtual drive
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d4-00000000 : The RAID controller detected one or more possible configuration problem
within the subsystem. Please check the event logs and if events are targeted to the same disk then
replace the drive. If necessary, contact technical support for additional assistance.([arg1],[arg2],
[arg3],[arg4],[arg5])
The RAID controller detected one or more possible configuration problem within the subsystem
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d5-00000000 : One or more virtual drive have problem. Please contact technical support to
resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
One or more virtual drive have problem
Severity
Info
Serviceable
No
Yes
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 400000d6-00000000 : Drive error was detected by RAID controller. Please contact technical
support to resolve this issue.([arg1],[arg2],[arg3],[arg4],[arg5])
Drive error was detected by RAID controller
Severity
Info
Serviceable
No
Yes
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
• 400000d7-00000000 : Drive error was detected by RAID controller. Please check the event logs and
if events are targeted to the same disk then replace the drive. If necessary, contact technical
support for additional assistance.([arg1],[arg2],[arg3],[arg4],[arg5])
Drive error was detected by RAID controller
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 80010002-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower non-critical)
has asserted. (CMOS Battery)
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
Serviceable
Yes
No
Alert Category
Warning - Voltage
SNMP Trap ID
13
CIM Information
Prefix: PLAT ID: 0476
User Response
Replace the system battery.
• 80010202-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted. (CMOS Battery)
This message is for the use case when an implementation has detected a Lower Critical sensor going low
has asserted.

Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Voltage
SNMP Trap ID
1
CIM Information
User Response
If the specified sensor is CMOS battery, replace the system battery. If the specified sensor is Planar
3.3V or Planar 5V, (trained technician only) replace the system board. If the specified sensor is Planar
12V, complete the following steps until the problem is solved:
1. Check power supply n LED.
2. Remove the failing power supply.
3. Follow actions in "Power Problems and Solving Power Problems".
4. (Trained technician only) Replace the system board. (n = power supply number)
SysBrd 12V : SysBrd 3.3V : SysBrd 5V :
• 80010204-1d01ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has
asserted. (Fan 1 Tach)
has asserted.
May also be shown as 800102041d01ffff or 0x800102041d01ffff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Fan Failure
SNMP Trap ID
11
CIM Information
User Response
1. Reseat the failing fan n, which is indicated by a lit LED near the fan connector on the system
board.
2. Replace the failing fan. (n = fan number)

has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
board.
has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
board.

has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
board.
• 80010701-0701ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical)
has asserted. (Ambient 1 Temp)
This message is for the use case when an implementation has detected an Upper Non-critical sensor
going high has asserted.
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Temperature
SNMP Trap ID
12
CIM Information
User Response
1. Reduce the ambient temperature.
2. Ensure the air baffle is installed correctly.
3. Check the server airflow. Make sure that nothing is blocking the air from coming into or
preventing the air from exiting the server.
has asserted. (PCIE Temp)

Severity
Warning
Serviceable
Yes
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
has asserted. (CPU VRM Temp)
Severity
Warning
Serviceable
Yes
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
has asserted. (Ambient 2 Temp)

Severity
Warning
Serviceable
Yes
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
• 80010701-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical)
has asserted. (PCH Temp)
Severity
Warning
Serviceable
Yes
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
• 80010901-0701ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has
asserted. (Ambient 1 Temp)

This message is for the use case when an implementation has detected an Upper Critical sensor going
high has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Temperature
SNMP Trap ID
0
CIM Information
User Response
asserted. (PCIE Temp)
high has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
asserted. (CPU VRM Temp)

high has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
asserted. (Ambient 2 Temp)
high has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 80010901-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has
asserted. (PCH Temp)

high has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
asserted. (SysBrd 12V)
high has asserted.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Voltage
SNMP Trap ID
1
CIM Information
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:

SysBrd 3.3V : SysBrd 5V :
• 80010b01-0701ffff : Numeric sensor [NumericSensorElementName] going high (upper non-
recoverable) has asserted. (Ambient 1 Temp)
This message is for the use case when an implementation has detected an Upper Non-recoverable sensor
May also be shown as 80010b010701ffff or 0x80010b010701ffff
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
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. Make sure that the heat sink for microprocessor n is installed correctly.
4. (Trained technician only) Replace system board.
recoverable) has asserted. (PCIE Temp)
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response

recoverable) has asserted. (CPU VRM Temp)
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
recoverable) has asserted. (Ambient 2 Temp)
Severity
Error
Serviceable
Yes
No
Alert Category

SNMP Trap ID
0
CIM Information
User Response
• 80010b01-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-
recoverable) has asserted. (PCH Temp)
May also be shown as 80010b012d01ffff or 0x80010b012d01ffff
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 80030006-2101ffff : Sensor [SensorElementName] has deasserted. (Sig Verify Fail)
This message is for the use case when an implementation has detected a Sensor has deasserted.
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
No action; information only.
• 80030012-2301ffff : Sensor [SensorElementName] has deasserted. (OS RealTime Mod)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 80030021-0782ffff : Sensor [SensorElementName] has deasserted. (PCIe Dev LK Down)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information

User Response
• 8003010c-2581ffff : Sensor [SensorElementName] has asserted. (Non-Auth DIMMs)
This message is for the use case when an implementation has detected a Sensor has asserted.
May also be shown as 8003010c2581ffff or 0x8003010c2581ffff
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
1. Replace the power supply with higher rated power.
2. Reduce the total power consumption by removing newly added or unused option like drives or
adapters.
• 8003010f-2101ffff : Sensor [SensorElementName] has asserted. (IMM FW Corrupted)
May also be shown as 8003010f2101ffff or 0x8003010f2101ffff
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
adapters.
• 80030112-0601ffff : Sensor [SensorElementName] has asserted. (SMM Mode)

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
adapters.
SMM Monitor :
• 80030121-0782ffff : Sensor [SensorElementName] has asserted. (PCIe Dev LK Down)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
adapters.
• 8007000d-2582ffff : Sensor [SensorElementName] has transitioned to normal state. (RAID Vol
State)
This message is for the use case when an implementation has detected a Sensor transition to the normal
state.
Severity
Info

Serviceable
No
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
• 8007010d-2582ffff : Sensor [SensorElementName] has transitioned from normal to non-critical
state. (RAID Vol State)
This message is for the use case when an implementation has detected a Sensor transitioned to non-
critical from normal.
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
None
• 8007010f-2201ffff : Sensor [SensorElementName] has transitioned from normal to non-critical
state. (GPT Status)
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Other

SNMP Trap ID
60
CIM Information
User Response
Complete the following step to solve PCI I/O resource errors:
1. Go to F1 Setup-> System Settings-> Device and I/O ports-> PCI 64 bit Resource and choose
enable.
• 8007010f-2582ffff : Sensor [SensorElementName] has transitioned from normal to non-critical
state. (I/O Resources)
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
Complete the following step to solve PCI I/O resource errors:
1. Go to F1 Setup-> System Settings-> Device and I/O ports-> PCI 64 bit Resource and choose
enable.
• 80070114-2201ffff : Sensor [SensorElementName] has transitioned from normal to non-critical
state. (TPM Phy Pres Set)
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Other
SNMP Trap ID
60

CIM Information
User Response
1. Complete the administrative tasks that require the TPM physical presence switch to be in the ON
position.
2. Restore the physical presence switch to the OFF position.
3. Reboot the system.
4. (Trained technician only) If the error continues, replace the planar.
• 80070128-2e01ffff : Sensor [SensorElementName] has transitioned from normal to non-critical
state. (ME Recovery)
May also be shown as 800701282e01ffff or 0x800701282e01ffff
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - Other
SNMP Trap ID
CIM Information
User Response
1. Restart IMM. If the error doesn't disappear, please proceed step 2.
2. Update to the latest level of iMM/uEFI code, please proceed step 3.
3. Replace node.
• 80070201-0301ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (CPU 1 OverTemp)
This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0

CIM Information
User Response
of the server), that the air baffles are in place and correctly installed, and that the server cover is
2. Check the ambient temperature. You must be operating within the specifications (see Features
and specifications for more information).
4. (Trained technician only) Replace microprocessor n. (n = microprocessor number)
state. (SysBrd Vol Fault)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Voltage
SNMP Trap ID
1
CIM Information
User Response
1. Check the system-event log.
2. Check for an error LED on the system board.
3. Replace any failing device.
4. Check for a server firmware update. Important: Some cluster solutions require specific code
levels or coordinated code updates. If the device is part of a cluster solution, verify that the latest
level of code is supported for the cluster solution before you update the code.
• 80070204-0a01ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (PS 1 Fan Fault)
from less severe.
May also be shown as 800702040a01ffff or 0x800702040a01ffff
Severity
Error
Serviceable
Yes

No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
1. Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-
supply fan.
2. Replace power supply n. (n = power supply number)
state. (PS 2 Fan Fault)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
supply fan.
state. (PS 1 Therm Fault)
from less severe.
Severity
Error
Serviceable
Yes
No

Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
supply fan.
2. Use the Lenovo Power Configurator utility to ensure current system power consumption is under
limitation. For more information and to download the utility, go to https://www.ibm.com/support/
entry/myportal/docdisplay?lndocid=LNVO-PWRCONF.
state. (PS 2 Therm Fault)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
supply fan.
2. Use the Lenovo Power Configurator utility to ensure current system power consumption is under
limitation. For more information and to download the utility, go to https://www.ibm.com/support/
entry/myportal/docdisplay?lndocid=LNVO-PWRCONF.
• 8007020d-2582ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (RAID Vol State)
from less severe.
Severity
Error

Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
None
• 8007020f-2201ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (TXT ACM Module)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. If enabling TXT is not required, disable TXT from the Setup Utility.
2. If enabling TXT is required, verify that the TPM is enabled and activated from the Setup Utility.
3. If the problem remains, contact your service representative.
• 8007020f-2582ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (I/O Resources)
from less severe.
Severity
Error
Serviceable
Yes
No

Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. If enabling TXT is not required, disable TXT from the Setup Utility.
2. If enabling TXT is required, verify that the TPM is enabled and activated from the Setup Utility.
3. If the problem remains, contact your service representative.
state. (TPM Lock)
from less severe.
Severity
Error
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. Update the server firmware (see Recovering the server firmware).
2. If the problem persists, (trained technician only) replace the system board (see Removing the
system board and Installing the system board).
state. (SysBrd Fault)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other

SNMP Trap ID
50
CIM Information
User Response
1. Check for an error LED on the system board.
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.
• 80070228-2e01ffff : Sensor [SensorElementName] has transitioned to critical from a less severe
state. (ME Error)
from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
If the specified sensor is IPMB IO Error, Me Error or ME Flash Error, complete the following steps until
the problem is solved:
1. Restart IMM. If the error still appears, proceed step 2.
2. Update the firmware (UEFI and IMM) to the latest level. If the error still appears, proceed step 3.
3. Replace the node.
ME Flash Error :
• 80070301-0301ffff : Sensor [SensorElementName] has transitioned to non-recoverable from a less
severe state. (CPU 1 OverTemp)
recoverable from less severe.
Severity
Error

Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 8007030d-2582ffff : Sensor [SensorElementName] has transitioned to non-recoverable from a less
severe state. (RAID Vol State)
recoverable from less severe.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
None
• 80070608-0a01ffff : Sensor [SensorElementName] has transitioned to non-recoverable. (PS1 12V
OC Fault)
recoverable.
Severity
Error

Serviceable
Yes
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
If the specified sensor is PS n 12V OC Fault, complete the following steps until the problem is solved:
1. Use the Lenovo Power Configurator utility to determine current system power consumption. For
more information and to download the utility, go to https://www.ibm.com/support/entry/
myportal/docdisplay?lndocid=LNVO-PWRCONF.
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
PS1 12V OV Fault : PS1 12V UV Fault : PS1 12Vaux Fault :
• 80070608-0a02ffff : Sensor [SensorElementName] has transitioned to non-recoverable. (PS2 12V
OC Fault)
recoverable.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Power
SNMP Trap ID

4
CIM Information
User Response
If the specified sensor is PS n 12V OC Fault, complete the following steps until the problem is solved:
1. Use the Lenovo Power Configurator utility to determine current system power consumption. For
more information and to download the utility, go to https://www.ibm.com/support/entry/
myportal/docdisplay?lndocid=LNVO-PWRCONF.
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
PS2 12V OV Fault : PS2 12V UV Fault : PS2 12Vaux Fault :
• 80070614-2201ffff : Sensor [SensorElementName] has transitioned to non-recoverable. (TPM Phy
Pres Set)
recoverable.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. Update the server firmware (see Recovering the server firmware).
2. If the problem persists, (trained technician only) replace the system board (see Removing the
system board and Installing the system board).

• 80080025-3701ffff : Device [LogicalDeviceElementName] has been removed from unit
[PhysicalPackageElementName]. (Thermal Board)
This message is for the use case when an implementation has detected a Device was removed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 80080125-3701ffff : Device [LogicalDeviceElementName] has been added. (Thermal Board)
This message is for the use case when an implementation has detected a Device was inserted.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 80080128-2101ffff : Device [LogicalDeviceElementName] has been added. (Low Security Jmp)
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 800b0008-1301ffff : Redundancy [RedundancySetElementName] has been restored. (Power Unit)
This message is for the use case when an implementation has detected Redundancy was Restored.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Redundant Power Supply
SNMP Trap ID
10
CIM Information
User Response
• 800b0108-1301ffff : Redundancy Lost for [RedundancySetElementName] has asserted. (Power
Unit)
This message is for the use case when Redundancy Lost has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Redundant Power Supply
SNMP Trap ID
9
CIM Information
User Response

1. Check the LEDs for both power supplies.
2. Follow the actions in Power-supply LEDs.
• 806f0007-0301ffff : [ProcessorElementName] has Failed with IERR. (CPU 1)
This message is for the use case when an implementation has detected a Processor Failed - IERR
Condition.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
1. Make sure that the latest level of firmware and device drivers are installed for all adapters and
standard devices, such as Ethernet, SCSI, and SAS. Important: Some cluster solutions require
specific code levels or coordinated 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. Update the firmware (UEFI and IMM) to the latest level (Updating the firmware).
3. Run the DSA program.
4. Reseat the adapter.
5. Replace the adapter.
6. (Trained technician only) Replace microprocessor n.
7. (Trained technician only) Replace the system board. (n = microprocessor number)
• 806f0008-0a01ffff : [PowerSupplyElementName] has been added to container
[PhysicalPackageElementName]. (Power Supply 1)
This message is for the use case when an implementation has detected a Power Supply has been added.
May also be shown as 806f00080a01ffff or 0x806f00080a01ffff
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

CIM Information
User Response
• 806f0008-0a02ffff : [PowerSupplyElementName] has been added to container
This message is for the use case when an implementation has detected a Power Supply has been added.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f0009-1301ffff : [PowerSupplyElementName] has been turned off. (Host Power)
This message is for the use case when an implementation has detected a Power Unit that has been
Disabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Power Off
SNMP Trap ID
23
CIM Information
User Response
• 806f000d-0400ffff : The Drive [StorageVolumeElementName] has been added. (Drive 0)
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
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22

CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
• 806f000d-0410ffff : The Drive [StorageVolumeElementName] has been added. (Ext Drive)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 806f000f-220101ff : The System [ComputerSystemElementName] has detected no memory in the
system. (ABR Status)
This message is for the use case when an implementation has detected that memory was detected in the
system.
May also be shown as 806f000f220101ff or 0x806f000f220101ff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
1. Make sure the server meets the minimum configuration to start (see Power-supply LEDs).
2. Recover the server firmware from the backup page: a. Restart the server. b. At the prompt, press
F3 to recover the firmware.
3. Update the server firmware on the primary page. Important: Some cluster solutions require

4. Remove components one at a time, restarting the server each time, to see if the problem goes
away.
5. If the problem remains, (trained technician only) replace the system board.
Firmware Error : Sys Boot Status :
• 806f000f-220102ff : Subsystem [MemoryElementName] has insufficient memory for operation.
(ABR Status)
This message is for the use case when an implementation has detected that the usable Memory is
insufficient for operation.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
• 806f000f-220103ff : The System [ComputerSystemElementName] encountered firmware error -
unrecoverable boot device failure. (ABR Status)
This message is for the use case when an implementation has detected that System Firmware Error
Unrecoverable boot device failure has occurred.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Hard Disk drive
SNMP Trap ID
5
CIM Information

User Response
This is a UEFI detected event. The UEFI(POST) error for this event can be found in the logged IMM
message text. Please refer to the UEFI(POST) error code in the "UEFI(POST) error code" section of
the Information Center for the appropriate user response. Firmware Error : Sys Boot Status :
• 806f000f-220104ff : The System [ComputerSystemElementName]has encountered a motherboard
failure. (ABR Status)
This message is for the use case when an implementation has detected that a fatal motherboard failure in
the system.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 806f000f-220107ff : The System [ComputerSystemElementName] encountered firmware error -
unrecoverable keyboard failure. (ABR Status)
This message is for the use case when an implementation has detected that System Firmware Error
Unrecoverable Keyboard failure has occurred.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response

• 806f000f-22010aff : The System [ComputerSystemElementName] encountered firmware error - no
video device detected. (ABR Status)
This message is for the use case when an implementation has detected that System Firmware Error No
video device detected has occurred.
May also be shown as 806f000f22010aff or 0x806f000f22010aff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 806f000f-22010bff : Firmware BIOS (ROM) corruption was detected on system
[ComputerSystemElementName] during POST. (ABR Status)
Firmware BIOS (ROM) corruption was detected on the system during POST.
May also be shown as 806f000f22010bff or 0x806f000f22010bff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
2. Recover the server firmware from the backup page: a.Restart the server. b.At the prompt, press
F3 to recover the firmware.

3. Update the server firmware to the latest level (see Updating the firmware). Important: Some
cluster solutions 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.
away.
5. If the problem remains, (trained service technician) replace the system board.
• 806f000f-22010cff : CPU voltage mismatch detected on [ProcessorElementName]. (ABR Status)
This message is for the use case when an implementation has detected a CPU voltage mismatch with the
socket voltage.
May also be shown as 806f000f22010cff or 0x806f000f22010cff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
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 : Sys Boot Status :
• 806f000f-2201ffff : The System [ComputerSystemElementName] encountered a POST Error. (ABR
Status)
This message is for the use case when an implementation has detected a Post Error.
May also be shown as 806f000f2201ffff or 0x806f000f2201ffff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information

User Response
This is a UEFI detected event. The UEFI(POST) error code for this event can be found in the logged
IMM message text. Please refer to the UEFI(POST) error code in the "UEFI(POST) error code" section
of the Information Center for the appropriate user response. Firmware Error : Sys Boot Status :
• 806f0013-1701ffff : A diagnostic interrupt has occurred on system
[ComputerSystemElementName]. (NMI State)
This message is for the use case when an implementation has detected a Front Panel NMI / Diagnostic
Interrupt.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
If the NMI button has not been pressed, complete the following steps:
1. Make sure that the NMI button is not pressed.
2. Replace the operator information panel cable.
3. Replace the operator information panel.
• 806f001e-2201ffff : No bootable media available for system [ComputerSystemElementName]. (No
Boot Device)
This message is for the use case when an implementation has detected a System with No Bootable
Media.
May also be shown as 806f001e2201ffff or 0x806f001e2201ffff
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

• 806f0021-2201ffff : Fault in slot [PhysicalConnectorSystemElementName] on system
[ComputerSystemElementName]. (No Op ROM Space)
This message is for the use case when an implementation has detected a Fault in a slot.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. Check the PCI LED.
2. Reseat the affected adapters and riser card.
3. Update the server firmware (UEFI and IMM) and adapter firmware. Important: Some cluster
update the code.
4. Replace the affected adapters.
5. Replace the riser card.
6. (Trained service technicians only) Replace the system board.
[ComputerSystemElementName]. (All PCI Error)
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information

User Response
update the code.
One of PCI Error :
[ComputerSystemElementName]. (PCI 1)
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
update the code.
Severity
Error

Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
update the code.
• 806f0023-2101ffff : Watchdog Timer expired for [WatchdogElementName]. (IPMI Watchdog)
This message is for the use case when an implementation has detected a Watchdog Timer Expired.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f0107-0301ffff : An Over-Temperature Condition has been detected on
[ProcessorElementName]. (CPU 1)
This message is for the use case when an implementation has detected an Over-Temperature Condition
Detected for Processor.
Severity
Error

Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
1. Make sure that the fans are operating. There are no obstructions to the airflow (front and rear of
the server), the air baffles are in place and correctly installed, and the server cover is installed and
completely closed.
• 806f0108-0a01ffff : [PowerSupplyElementName] has Failed. (Power Supply 1)
This message is for the use case when an implementation has detected a Power Supply has failed.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
1. Reseat power supply n.
2. If the power-on LED is not lit and the power-supply error LED is lit, replace power supply n.
3. If both the power-on LED and the power-supply error LED are not lit, see Power problems for
more information. (n = power supply number)
• 806f0108-0a02ffff : [PowerSupplyElementName] has Failed. (Power Supply 2)
This message is for the use case when an implementation has detected a Power Supply has failed.
Severity
Error
Serviceable
Yes

Yes
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
1. Reseat power supply n.
2. If the power-on LED is not lit and the power-supply error LED is lit, replace power supply n.
3. If both the power-on LED and the power-supply error LED are not lit, see Power problems for
more information. (n = power supply number)
• 806f0109-1301ffff : [PowerSupplyElementName] has been Power Cycled. (Host Power)
This message is for the use case when an implementation has detected a Power Unit that has been power
cycled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f010c-2001ffff : Uncorrectable error detected for [PhysicalMemoryElementName] on
Subsystem [MemoryElementName]. (DIMM 1)
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
Serviceable
Yes
Yes
Alert Category
Critical - Memory

SNMP Trap ID
41
CIM Information
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. Refer to TIP H212293 for minimum code level.
2. Check the Lenovo support website for an applicable retain tip or firmware update that applies to
this memory error.
3. Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs)
to a different memory channel or microprocessor.
4. If the problem follows the DIMM, replace the failing DIMM.
5. (Trained technician only) If the problem occurs on the same DIMM connector, check the DIMM
connector. If the connector contains any foreign material or is damaged, replace the system
board.
6. (Trained technician only) Remove the affected microprocessor and check the microprocessor
socket pins for any damaged pins. If a damage is found, replace the system board.
7. (Trained technician only) Replace the affected microprocessor.
8. Manually re-enable all affected DIMMs if the server firmware version is older than UEFI v1.10. If
the server firmware version is UEFI v1.10 or newer, disconnect and reconnect the server to the
power source and restart the server.
9. (Trained Service technician only) Replace the affected microprocessor.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.

board.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
board.

Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
board.
Subsystem [MemoryElementName]. (All DIMMS)
Severity
Error

Serviceable
Yes
Yes
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
board.
One of the DIMMs :
• 806f010d-0400ffff : The Drive [StorageVolumeElementName] has been disabled due to a detected
fault. (Drive 0)
This message is for the use case when an implementation has detected a Drive was Disabled due to fault.
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information

User Response
1. Run the hard disk drive diagnostic test on drive n.
2. Reseat the following components: a. Hard disk drive (wait 1 minute or more before reinstalling
the drive) b. Cable from the system board to the backplane
3. Replace the following components one at a time, in the order shown, restarting the server each
time: a. Hard disk drive b. Cable from the system board to the backplane c. Hard disk drive
backplane (n = hard disk drive number)
fault. (Drive 1)
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
fault. (Drive 2)
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID

5
CIM Information
User Response
fault. (Drive 3)
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
fault. (Drive 4)
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
fault. (Drive 5)
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
fault. (Drive 6)
Severity
Error
Serviceable
Yes

Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
fault. (Drive 7)
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
fault. (Ext Drive)
Severity
Error
Serviceable

Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 806f010f-2201ffff : The System [ComputerSystemElementName] encountered a firmware hang.
(Firmware Error)
This message is for the use case when an implementation has detected a System Firmware Hang.
Severity
Error
Serviceable
Yes
No
Alert Category
System - Boot failure
SNMP Trap ID
25
CIM Information
User Response
• 806f0123-2101ffff : Reboot of system [ComputerSystemElementName] initiated by
[WatchdogElementName]. (IPMI Watchdog)
This message is for the use case when an implementation has detected a Reboot by a Watchdog
occurred.
Severity

Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f0125-1001ffff : [ManagedElementName] detected as absent. (PCI Riser 1)
This message is for the use case when an implementation has detected a Managed Element is Absent.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
If there is no GPU/storage tray installed in the system, then the log event is a normal condition. If
there is a GPU/storage tray installed in the system, then check the following two portions:
1. PDB (Power Distribution Board) cable is correctly connected from riser card to PDB.
2. Replace another PDB cable.
• 806f0207-0301ffff : [ProcessorElementName] has Failed with FRB1/BIST condition. (CPU 1)
This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST
condition.
Severity
Error
Serviceable
Yes
Yes

Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
1. Make sure that the latest levels of firmware and device drivers are installed for all adapters and
standard devices, such as Ethernet, SCSI, and SAS. Important: Some cluster solutions require
2. Update the firmware (UEFI and IMM) to the latest level (Updating the firmware).
3. Run the DSA program.
4. Reseat the adapter.
6. (Trained technician only) Replace microprocessor n.
7. (Trained technician only) Replace the system board. (n = microprocessor number)
• 806f020d-0400ffff : Failure Predicted on drive [StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive 0)
This message is for the use case when an implementation has detected an Array Failure is Predicted.
Severity
Warning
Serviceable
Yes
Yes
Alert Category
System - Predicted Failure
SNMP Trap ID
27
CIM Information
User Response

Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response

Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response

Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response

Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response
[ComputerSystemElementName]. (Ext Drive)
Severity
Warning
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
27
CIM Information
User Response

• 806f0223-2101ffff : Powering off system [ComputerSystemElementName] initiated by
This message is for the use case when an implementation has detected a Poweroff by Watchdog has
occurred.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f0308-0a01ffff : [PowerSupplyElementName] has lost input. (Power Supply 1)
This message is for the use case when an implementation has detected a Power Supply that has input
that has been lost.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
3. See Power-supply LEDs for more information. (n = power supply number)

• 806f0308-0a02ffff : [PowerSupplyElementName] has lost input. (Power Supply 2)
that has been lost.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
3. See Power-supply LEDs for more information. (n = power supply number)
• 806f030c-2001ffff : Scrub Failure for [PhysicalMemoryElementName] on Subsystem
This message is for the use case when an implementation has detected a Memory Scrub failure.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.

3. Make sure that the DIMMs are firmly seated and no foreign material is found in the DIMM
connector. Then, retry with the same DIMM.
4. If the problem is related to a DIMM, replace the failing DIMM indicated by the error LEDs.
5. If the problem occurs on the same DIMM connector, swap the affected DIMMs (as indicated by
the error LEDs on the system board or the event logs) to a different memory channel or
microprocessor.
board.
7. (Trained service technician only) Remove the affected microprocessor and check the
microprocessor socket pins for any damaged pins. If a damage is found, replace the system
board.
8. (Trained service technician only) If the problem is related to microprocessor socket pins, replace
the system board.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
microprocessor.
board.

board.
the system board.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
microprocessor.
board.
board.
the system board.

Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
this memory error.
microprocessor.
board.
board.
the system board.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID

41
CIM Information
User Response
this memory error.
microprocessor.
board.
board.
the system board.
One of the DIMMs :
• 806f030d-0400ffff : Hot Spare enabled for [ComputerSystemElementName]. (Drive 0)
This message is for the use case when an implementation has detected a Hot Spare has been Enabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f030d-0410ffff : Hot Spare enabled for [ComputerSystemElementName]. (Ext Drive)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information

User Response
• 806f0313-1701ffff : A software NMI has occurred on system [ComputerSystemElementName]. (NMI
State)
This message is for the use case when an implementation has detected a Software NMI.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
1. Check the device driver.
2. Reinstall the device driver.
3. Update all device drivers to the latest level.
4. Update the firmware (UEFI and IMM).
• 806f0323-2101ffff : Power cycle of system [ComputerSystemElementName] initiated by watchdog
This message is for the use case when an implementation has detected a Power Cycle by Watchdog
occurred.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f040c-2001ffff : [PhysicalMemoryElementName] Disabled on Subsystem

This message is for the use case when an implementation has detected that Memory has been Disabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
1. Make sure the DIMM is installed correctly.
2. If the DIMM was disabled because of a memory fault (memory uncorrectable error or memory
logging limit reached), follow the suggested actions for that error event and restart the server.
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.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
One of the DIMMs :
• 806f0413-2582ffff : A PCI PERR has occurred on system [ComputerSystemElementName]. (PCIs)
This message is for the use case when an implementation has detected a PCI PERR.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response

2. Reseat the affected adapters and riser cards.
update the code.
4. Remove both adapters.
5. Replace the PCIe adapters.
• 806f0507-0301ffff : [ProcessorElementName] has a Configuration Mismatch. (CPU 1)
This message is for the use case when an implementation has detected a Processor Configuration
Mismatch has occurred.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
1. Check the CPU LED. See more information about the CPU LED in Light path diagnostics.
3. Make sure that the installed microprocessors are compatible with each other.
4. (Trained technician only) Reseat microprocessor n.
• 806f050c-2001ffff : Memory Logging Limit Reached for [PhysicalMemoryElementName] on
This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Reached.
Severity
Warning
Serviceable
Yes
Yes
Alert Category

Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
this memory error.
4. If the error still occurs on the same DIMM, replace the affected DIMM.
board.
has been Reached.
Severity
Warning
Serviceable
Yes
Yes
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
this memory error.

board.
has been Reached.
Severity
Warning
Serviceable
Yes
Yes
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
this memory error.
board.
has been Reached.
Severity

Warning
Serviceable
Yes
Yes
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
this memory error.
board.
has been Reached.
Severity
Warning
Serviceable
Yes
Yes
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response

this memory error.
board.
One of the DIMMs :
• 806f050d-0400ffff : Array [ComputerSystemElementName] is in critical condition. (Drive 0)
This message is for the use case when an implementation has detected that an Array is Critical.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
1. Make sure that the RAID adapter firmware and hard disk drive firmware are at the latest level.
2. Make sure that the SAS cable is connected correctly.
3. Replace the SAS cable.
4. Check backplane cable connection.
5. Replace the RAID adapter.
6. Replace the hard disk drive that is indicated by a lit status LED.
Severity
Error
Serviceable

Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity

Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 806f050d-0410ffff : Array [ComputerSystemElementName] is in critical condition. (Ext Drive)
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

• 806f0513-2582ffff : A PCI SERR has occurred on system [ComputerSystemElementName]. (PCIs)
This message is for the use case when an implementation has detected a PCI SERR.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
update the code.
4. Make sure that the adapter is supported. For a list of supported optional devices, see http://
www.lenovo.com/serverproven/.
5. Remove both adapters.
6. Replace the PCIe adapters.
• 806f052b-2101ffff : Invalid or Unsupported firmware or software was detected on system
[ComputerSystemElementName]. (IMM2 FW Failover)
This message is for the use case when an implementation has detected an Invalid/Unsupported Firmware/
Software Version.
May also be shown as 806f052b2101ffff or 0x806f052b2101ffff
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Other
SNMP Trap ID
50

CIM Information
User Response
2. Recover the server firmware from the backup page by restarting the server.
3. Update the server firmware to the latest level (see Updating the firmware). Important: Some
cluster solutions 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.
away.
5. If the problem remains, (trained service technician) replace the system board.
• 806f0607-0301ffff : An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName]
has asserted. (CPU 1)
This message is for the use case when an SM BIOS Uncorrectable CPU complex error has asserted.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
1. Make sure that the installed microprocessors are compatible with each other (see Installing a
microprocessor and heat sink for information about microprocessor requirements).
2. Update the server firmware to the latest level (see Updating the firmware).
3. (Trained technician only) Replace the incompatible microprocessor.
• 806f060d-0400ffff : Array [ComputerSystemElementName] has failed. (Drive 0)
This message is for the use case when an implementation has detected that an Array Failed.
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
Severity
Error
Serviceable
Yes
Yes
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 806f060d-0410ffff : Array [ComputerSystemElementName] has failed. (Ext Drive)
Severity
Error
Serviceable
Yes
Yes
Alert Category

SNMP Trap ID
5
CIM Information
User Response
• 806f070c-2001ffff : Configuration Error for [PhysicalMemoryElementName] on Subsystem
This message is for the use case when an implementation has detected a Memory DIMM configuration
error has been corrected.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
Make sure that DIMMs are installed in the correct sequence and have the same size, type, speed, and
technology.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID

41
CIM Information
User Response
technology.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
technology.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response

technology.
Severity
Error
Serviceable
Yes
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
technology. One of the DIMMs :
• 806f070d-0400ffff : Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive
0)
This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
1)
Progress.

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
2)
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
3)
Progress.
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
4)
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
5)
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

CIM Information
User Response
6)
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
7)
Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f070d-0410ffff : Rebuild in progress for Array in system [ComputerSystemElementName]. (Ext
Drive)

Progress.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f072b-2101ffff : A successful software or firmware change was detected on system
[ComputerSystemElementName]. (IMM Promotion)
This message is for the use case when an implementation has detected a Successful Software or
Firmware Change.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
No action; information only. IMM Recovery :
• 806f072b-2201ffff : A successful software or firmware change was detected on system
[ComputerSystemElementName]. (Bkup Auto Update)
This message is for the use case when an implementation has detected a Successful Software or
Firmware Change.
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
No action; information only. ROM Recovery :
• 806f0807-0301ffff : [ProcessorElementName] has been Disabled. (CPU 1)
This message is for the use case when an implementation has detected a Processor has been Disabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f0813-2582ffff : An Uncorrectable Bus Error has occurred on system
This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information

User Response
2. (Trained technician only) Remove the failing microprocessor from the system board (see
Removing a microprocessor and heat sink).
4. Make sure that the two microprocessors are matching.
• 806f0813-2584ffff : An Uncorrectable Bus Error has occurred on system
[ComputerSystemElementName]. (CPUs)
This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
Severity
Error
Serviceable
Yes
Yes
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
2. (Trained technician only) Remove the failing microprocessor from the system board (see
Removing a microprocessor and heat sink).
4. Make sure that the two microprocessors are matching.
• 806f0823-2101ffff : Watchdog Timer interrupt occurred for [WatchdogElementName]. (IPMI
Watchdog)
This message is for the use case when an implementation has detected a Watchdog Timer interrupt
occurred.
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 806f090c-2001ffff : [PhysicalMemoryElementName] on Subsystem [MemoryElementName]
Throttled. (DIMM 1)
This message is for the use case when an implementation has detected Memory has been Throttled.
Severity
Warning
Serviceable
Yes
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
1. Reseat the DIMM, and then restart the server.
2. Replace DIMM n. (n = DIMM number)
Throttled. (DIMM 2)
Severity
Warning
Serviceable
Yes
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
Throttled. (DIMM 3)
Severity
Warning
Serviceable
Yes
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
Throttled. (DIMM 4)
Severity
Warning
Serviceable
Yes
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
• 806f0a07-0301ffff : [ProcessorElementName] is operating in a Degraded State. (CPU 1)

This message is for the use case when an implementation has detected a Processor is running in the
Degraded state.
Severity
Warning
Serviceable
Yes
No
Alert Category
Warning - CPU
SNMP Trap ID
42
CIM Information
User Response
of the server), that the air baffles are in place and correctly installed, and that the server cover is
2. Check the ambient temperature. You must be operating within the specifications.
• 806f0a0c-2001ffff : An Over-Temperature Condition has been detected on the
[PhysicalMemoryElementName] on Subsystem [MemoryElementName]. (DIMM 1)
This message is for the use case when an implementation has detected an Over Temperature Condition
for Memory that has been Detected.
May also be shown as 806f0a0c2001ffff or 0x806f0a0c2001ffff
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
1. Make sure that the fans are operating, that there are no obstructions to the airflow, that the air
baffles are in place and correctly installed, and that the server cover is installed and completely
closed.
2. Make sure that ambient temperature is within the specifications.

3. If a fan has failed, complete the action for a fan failure.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
closed.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response

closed.
Severity
Error
Serviceable
Yes
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
closed.
• 81010002-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower non-critical)
has deasserted. (CMOS Battery)
This message is for the use case when an implementation has detected a Lower Non-critical sensor going
low has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Voltage
SNMP Trap ID

13
CIM Information
User Response
• 81010202-0701ffff : Numeric sensor [NumericSensorElementName] going low (lower critical) has
deasserted. (CMOS Battery)
has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Voltage
SNMP Trap ID
1
CIM Information
User Response
No action; information only. SysBrd 12V : SysBrd 3.3V : SysBrd 5V :
deasserted. (Fan 1 Tach)
has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response

has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
has deasserted.
Severity

Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
has deasserted. (Ambient 1 Temp)
going high has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
has deasserted. (PCIE Temp)
Severity
Info
Serviceable
No
No
Alert Category

SNMP Trap ID
12
CIM Information
User Response
has deasserted. (CPU VRM Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
has deasserted. (Ambient 2 Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response

• 81010701-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-critical)
has deasserted. (PCH Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
12
CIM Information
User Response
deasserted. (Ambient 1 Temp)
high has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
deasserted. (PCIE Temp)

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
deasserted. (CPU VRM Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
deasserted. (Ambient 2 Temp)
Severity
Info
Serviceable
No
No

Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 81010901-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper critical) has
deasserted. (PCH Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
deasserted. (SysBrd 12V)
Severity
Info
Serviceable
No
No
Alert Category
Critical - Voltage
SNMP Trap ID
1
CIM Information

User Response
No action; information only. SysBrd 3.3V : SysBrd 5V :
recoverable) has deasserted. (Ambient 1 Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
recoverable) has deasserted. (PCIE Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
recoverable) has deasserted. (CPU VRM Temp)

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
recoverable) has deasserted. (Ambient 2 Temp)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 81010b01-2d01ffff : Numeric sensor [NumericSensorElementName] going high (upper non-
recoverable) has deasserted. (PCH Temp)
May also be shown as 81010b012d01ffff or 0x81010b012d01ffff
Severity
Info
Serviceable
No
No

Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 81030006-2101ffff : Sensor [SensorElementName] has asserted. (Sig Verify Fail)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 81030012-2301ffff : Sensor [SensorElementName] has asserted. (OS RealTime Mod)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 81030021-0782ffff : Sensor [SensorElementName] has asserted. (PCIe Dev LK Down)

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 8103010c-2581ffff : Sensor [SensorElementName] has deasserted. (Non-Auth DIMMs)
May also be shown as 8103010c2581ffff or 0x8103010c2581ffff
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 81030112-0601ffff : Sensor [SensorElementName] has deasserted. (SMM Mode)
Severity
Info
Serviceable
No
No
Alert Category
System - Other

SNMP Trap ID
CIM Information
User Response
No action; information only. SMM Monitor :
• 81030121-0782ffff : Sensor [SensorElementName] has deasserted. (PCIe Dev LK Down)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 8107010d-2582ffff : Sensor [SensorElementName] has deasserted the transition from normal to
non-critical state. (RAID Vol State)
This message is for the use case when an implementation has detected that a Sensor has deasserted a
transition to non-critical from normal.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
• 8107010f-2201ffff : Sensor [SensorElementName] has deasserted the transition from normal to
non-critical state. (GPT Status)

Severity
Info
Serviceable
No
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
• 8107010f-2582ffff : Sensor [SensorElementName] has deasserted the transition from normal to
non-critical state. (I/O Resources)
Severity
Info
Serviceable
No
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
• 81070128-2e01ffff : Sensor [SensorElementName] has deasserted the transition from normal to
non-critical state. (ME Recovery)
Severity
Info
Serviceable

No
No
Alert Category
Warning - Other
SNMP Trap ID
60
CIM Information
User Response
• 81070201-0301ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (CPU 1 OverTemp)
This message is for the use case when an implementation has detected a Sensor transition to less severe
from critical.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
critical. (SysBrd Vol Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Voltage
SNMP Trap ID

1
CIM Information
User Response
• 81070204-0a01ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (PS 1 Fan Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response
critical. (PS 2 Fan Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
11
CIM Information
User Response

critical. (PS 1 Therm Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
critical. (PS 2 Therm Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
• 8107020d-2582ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (RAID Vol State)
from critical.
Severity

Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 8107020f-2201ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (TXT ACM Module)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 8107020f-2582ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (I/O Resources)
from critical.
Severity
Info
Serviceable
No
No
Alert Category

Critical - Other
SNMP Trap ID
50
CIM Information
User Response
critical. (TPM Lock)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
critical. (SysBrd Fault)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response

• 81070228-2e01ffff : Sensor [SensorElementName] has transitioned to a less severe state from
critical. (ME Error)
from critical.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
No action; information only. ME Flash Error :
• 81070301-0301ffff : Sensor [SensorElementName] has deasserted the transition to non-
recoverable from a less severe state. (CPU 1 OverTemp)
This message is for the use case when an implementation has detected that the Sensor transition to non-
recoverable from less severe has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 8107030d-2582ffff : Sensor [SensorElementName] has deasserted the transition to non-
recoverable from a less severe state. (RAID Vol State)
recoverable from less severe has deasserted.

Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 81070608-0a01ffff : Sensor [SensorElementName] has deasserted the transition to non-
recoverable. (PS1 12V OC Fault)
recoverable has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
No action; information only. PS1 12V OV Fault : PS1 12V UV Fault : PS1 12Vaux Fault :
• 81070608-0a02ffff : Sensor [SensorElementName] has deasserted the transition to non-
recoverable. (PS2 12V OC Fault)
recoverable has deasserted.
Severity
Info
Serviceable
No
No

Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
No action; information only. PS2 12V OV Fault : PS2 12V UV Fault : PS2 12Vaux Fault :
• 81080025-3701ffff : Device [LogicalDeviceElementName] has been added. (Thermal Board)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 81080125-3701ffff : Device [LogicalDeviceElementName] has been removed from unit
[PhysicalPackageElementName]. (Thermal Board)
This message is for the use case when an implementation has detected a Device was removed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0007-0301ffff : [ProcessorElementName] has Recovered from IERR. (CPU 1)

This message is for the use case when an implementation has detected a Processor Recovered - IERR
Condition.
Severity
Info
Serviceable
No
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
• 816f0008-0a01ffff : [PowerSupplyElementName] has been removed from container
This message is for the use case when an implementation has detected a Power Supply has been
removed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0008-0a02ffff : [PowerSupplyElementName] has been removed from container
This message is for the use case when an implementation has detected a Power Supply has been
removed.
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0009-1301ffff : [PowerSupplyElementName] has been turned on. (Host Power)
This message is for the use case when an implementation has detected a Power Unit that has been
Enabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Power On
SNMP Trap ID
24
CIM Information
User Response
• 816f000d-0400ffff : The Drive [StorageVolumeElementName] has been removed from unit
[PhysicalPackageElementName]. (Drive 0)
This message is for the use case when an implementation has detected a Drive has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information

User Response
1. Reseat hard disk drive n.(n = hard disk drive number). Wait 1 minute or more before reinstalling
the drive.
2. Replace the hard disk drive.
3. Make sure that the disk firmware and RAID controller firmware are at the latest level.
4. Check the SAS cable.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22

CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

22
CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other

SNMP Trap ID
22
CIM Information
User Response
the drive.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
22
CIM Information
User Response
the drive.
[PhysicalPackageElementName]. (Ext Drive)
Severity
Info
Serviceable
No
No
Alert Category

System - Other
SNMP Trap ID
22
CIM Information
User Response
the drive.
• 816f000f-2201ffff : The System [ComputerSystemElementName] has detected a POST Error
deassertion. (ABR Status)
This message is for the use case when an implementation has detected that Post Error has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
No action; information only. Firmware Error : Sys Boot Status :
• 816f0013-1701ffff : System [ComputerSystemElementName] has recovered from a diagnostic
interrupt. (NMI State)
This message is for the use case when an implementation has detected a recovery from a Front Panel NMI
/ Diagnostic Interrupt
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50

CIM Information
User Response
• 816f0021-2201ffff : Fault condition removed on slot [PhysicalConnectorElementName] on system
[ComputerSystemElementName]. (No Op ROM Space)
This message is for the use case when an implementation has detected a Fault condition in a slot has
been removed.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
[ComputerSystemElementName]. (All PCI Error)
been removed.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
No action; information only. One of PCI Error :

been removed.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
been removed.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 816f0107-0301ffff : An Over-Temperature Condition has been removed on
[ProcessorElementName]. (CPU 1)
This message is for the use case when an implementation has detected a Over-Temperature Condition
has been Removed for Processor.
Severity
Info
Serviceable

No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
• 816f0108-0a01ffff : [PowerSupplyElementName] has returned to OK status. (Power Supply 1)
This message is for the use case when an implementation has detected a Power Supply return to normal
operational status.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information
User Response
• 816f0108-0a02ffff : [PowerSupplyElementName] has returned to OK status. (Power Supply 2)
This message is for the use case when an implementation has detected a Power Supply return to normal
operational status.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Power
SNMP Trap ID
4
CIM Information

User Response
• 816f010c-2001ffff : Uncorrectable error recovery detected for [PhysicalMemoryElementName] on
This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
recovery.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
recovery.

Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
recovery.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
recovery.
Severity
Info
Serviceable
No

No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
No action; information only. One of the DIMMs :
• 816f010d-0400ffff : The Drive [StorageVolumeElementName] has been enabled. (Drive 0)
This message is for the use case when an implementation has detected a Drive was Enabled.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Info
Serviceable
No

No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 816f010d-0410ffff : The Drive [StorageVolumeElementName] has been enabled. (Ext Drive)
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 816f010f-2201ffff : The System [ComputerSystemElementName] has recovered from a firmware
hang. (Firmware Error)
This message is for the use case when an implementation has recovered from a System Firmware Hang.
Severity
Info
Serviceable
No

No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 816f0125-1001ffff : [ManagedElementName] detected as present. (PCI Riser 1)
This message is for the use case when an implementation has detected a Managed Element is now
Present.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0207-0301ffff : [ProcessorElementName] has Recovered from FRB1/BIST condition. (CPU 1)
This message is for the use case when an implementation has detected a Processor Recovered - FRB1/
BIST condition.
Severity
Info
Serviceable
No
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information

User Response
• 816f020d-0400ffff : Failure no longer Predicted on drive [StorageVolumeElementName] for array
This message is for the use case when an implementation has detected an Array Failure is no longer
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.
Severity
Info
Serviceable
No
No

Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information

User Response
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
[ComputerSystemElementName]. (Ext Drive)
Predicted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
27
CIM Information
User Response
• 816f0308-0a01ffff : [PowerSupplyElementName] has returned to a Normal Input State. (Power
Supply 1)
that has returned to normal.

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0308-0a02ffff : [PowerSupplyElementName] has returned to a Normal Input State. (Power
Supply 2)
that has returned to normal.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
[MemoryElementName] has recovered. (DIMM 1)
This message is for the use case when an implementation has detected a Memory Scrub failure recovery.
Severity
Info
Serviceable
No
No
Alert Category

Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
[MemoryElementName] has recovered. (All DIMMS)
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
• 816f030d-0400ffff : Hot spare disabled for [ComputerSystemElementName]. (Drive 0)
This message is for the use case when an implementation has detected a Hot Spare has been Disabled.
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No

No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

• 816f030d-0410ffff : Hot spare disabled for [ComputerSystemElementName]. (Ext Drive)
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0313-1701ffff : System [ComputerSystemElementName] has recovered from an NMI. (NMI
State)
This message is for the use case when an implementation has detected a Software NMI has been
Recovered from.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 816f040c-2001ffff : [PhysicalMemoryElementName] Enabled on Subsystem
This message is for the use case when an implementation has detected that Memory has been Enabled.
Severity
Info
Serviceable

No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information

User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0413-2582ffff : A PCI PERR recovery has occurred on system
This message is for the use case when an implementation has detected a PCI PERR recovered.

Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 816f0507-0301ffff : [ProcessorElementName] has Recovered from a Configuration Mismatch. (CPU
1)
This message is for the use case when an implementation has Recovered from a Processor Configuration
Mismatch.
Severity
Info
Serviceable
No
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
• 816f050c-2001ffff : Memory Logging Limit Removed for [PhysicalMemoryElementName] on
has been Removed.
Severity
Info
Serviceable
No
No

Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information

User Response
has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
Warning - Memory
SNMP Trap ID
43
CIM Information
User Response
• 816f050d-0400ffff : Critical Array [ComputerSystemElementName] has deasserted. (Drive 0)
This message is for the use case when an implementation has detected that an Critiacal Array has
deasserted.

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No
No
Alert Category

SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response

deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
deasserted.
Severity
Info
Serviceable
No

No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 816f050d-0410ffff : Critical Array [ComputerSystemElementName] has deasserted. (Ext Drive)
deasserted.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 816f0513-2582ffff : A PCI SERR on system [ComputerSystemElementName] has deasserted. (PCIs)
This message is for the use case when an implementation has detected a PCI SERR deassertion.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information

User Response
• 816f0607-0301ffff : An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName]
has deasserted. (CPU 1)
This message is for the use case when an SM BIOS Uncorrectable CPU complex error has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Critical - CPU
SNMP Trap ID
40
CIM Information
User Response
• 816f060d-0400ffff : Array in system [ComputerSystemElementName] has been restored. (Drive 0)
This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.
Severity
Info

Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5

CIM Information
User Response
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
Restored.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
5
CIM Information
User Response
• 816f060d-0410ffff : Array in system [ComputerSystemElementName] has been restored. (Ext Drive)
Restored.
Severity
Info
Serviceable
No
No
Alert Category

SNMP Trap ID
5
CIM Information
User Response
• 816f070c-2001ffff : Configuration error for [PhysicalMemoryElementName] on Subsystem
[MemoryElementName]has deasserted. (DIMM 1)
error has deasserted.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
[MemoryElementName]has deasserted. (All DIMMS)
Severity

Info
Serviceable
No
No
Alert Category
Critical - Memory
SNMP Trap ID
41
CIM Information
User Response
• 816f070d-0400ffff : Rebuild completed for Array in system [ComputerSystemElementName]. (Drive
0)
This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
1)
Completed.
Severity
Info
Serviceable
No
No
Alert Category

System - Other
SNMP Trap ID
CIM Information
User Response
2)
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
3)
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response

4)
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
5)
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
6)
Completed.

Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
7)
Completed.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f070d-0410ffff : Rebuild completed for Array in system [ComputerSystemElementName]. (Ext
Drive)
Completed.
Severity
Info
Serviceable
No
No

Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0807-0301ffff : [ProcessorElementName] has been Enabled. (CPU 1)
This message is for the use case when an implementation has detected a Processor has been Enabled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
• 816f0813-2582ffff : System [ComputerSystemElementName] has recovered from an Uncorrectable
Bus Error. (PCIs)
This message is for the use case when an implementation has detected a that a system has recovered
from a Bus Uncorrectable Error.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response

• 816f0813-2584ffff : System [ComputerSystemElementName] has recovered from an Uncorrectable
Bus Error. (CPUs)
This message is for the use case when an implementation has detected a that a system has recovered
from a Bus Uncorrectable Error.
Severity
Info
Serviceable
No
No
Alert Category
Critical - Other
SNMP Trap ID
50
CIM Information
User Response
• 816f090c-2001ffff : [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no
longer Throttled. (DIMM 1)
This message is for the use case when an implementation has detected Memory is no longer Throttled.
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info

Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
System - Other
SNMP Trap ID

CIM Information
User Response
• 816f0a07-0301ffff : The Processor [ProcessorElementName] is no longer operating in a Degraded
State. (CPU 1)
This message is for the use case when an implementation has detected a Processor is no longer running
in the Degraded state.
Severity
Info
Serviceable
No
No
Alert Category
Warning - CPU
SNMP Trap ID
42
CIM Information
User Response
• 816f0a0c-2001ffff : An Over-Temperature Condition has been removed on the
for Memory that has been Removed.
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response

Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
Severity
Info
Serviceable
No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response
Severity
Info
Serviceable

No
No
Alert Category
SNMP Trap ID
0
CIM Information
User Response

Appendix B. UEFI (POST) error codes
This section details the UEFI (POST) error codes.
UEFI (POST) diagnostic error codes can be generated when the server starts up or while the server is
running. UEFI (POST) codes are logged in the IMM2.1 event log in the server.
For each event code, the following fields are displayed:
Event identifier
An identifier that uniquely identifies an event.
Event description
The logged message string that appears for an event.
Explanation
Additional information to explain why the event occurred.
Severity
An indication of the level of concern for the condition. The severity is abbreviated in the event log to the
first character. The following severities can be displayed:
Table 30. Event severity levels
Severity Description
Informational An informational message is something that was recorded for audit purposes,
usually a user action or a change of states that is normal behavior.
Warning A warning is not as severe as an error, but if possible, the condition should be
corrected before it becomes an error. It might also be a condition that requires
additional monitoring or maintenance.
Error An error typically indicates a failure or critical condition that impairs service or an
expected function.
User response
Indicate the actions that you should take to resolve the event.
Perform the steps listed in this section in the order shown until the problem is solved. After you perform
all of the actions that are described in this field, if you cannot solve the problem, contact IBM support.
The following is the list of the UEFI (POST) error codes and suggested actions to correct the detected
problems.
List of UEFI events

This section lists all messages that can be sent from UEFI.
• I.2018002 [I.2018002]
Explanation: 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 %. OUT_OF_RESOURCES (PCI Option
ROM)

Severity
Info
User Response
Complete the following steps:
1. If this PCIe device and/or any attached cables were recently installed, moved, serviced or
upgraded, reseat the 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 Lenovo XClarity Essentials OneCLI or using adapter manufacturer utilities so that
adapter firmware can be updated.
3. Move the adapter to a different slot. If a slot is not available or error recurs, replace the adapter.
4. If the adapter was moved to a different slot and the error did not recur, verify that this is not a
system limitation. Then replace the system board. Also, if this is not the initial installation and the
error persists after adapter replacement, replace the system board.
• I.2018003 [I.2018003]
Explanation: A bad option ROM checksum was detected for the device found at Bus % Device %
Function %. The Vendor ID for the device is % and the Device ID is %. ROM CHECKSUM ERROR
Severity
Error
User Response
1. If this PCIe device and/or any attached cables were recently installed, moved, serviced or
upgraded, reseat the adapter and any attached cables.
2. Move the adapter to a different system slot, if available.
3. Check IBM support site for any applicable service bulletin or UEFI or adapter firmware update
that applies to this error. NOTE: It may be necessary to configure slot to Gen1 or to use special
utility software so that adapter firmware can be upgraded. Gen1/Gen2 settings can be
configured via F1 Setup -> System Settings -> Devices and I/O Ports -> PCIe Gen1/Gen2/Gen3
Speed Selection, or the Lenovo XClarity Essentials OneCLI Utility.
• I.3818001 [I.3818001]
Explanation: The firmware image capsule signature for the currently booted flash bank is invalid. Current
Bank CRTM Capsule Update Signature Invalid
Severity
Info
User Response
1. Reboot the system. Will come up on backup UEFI image. Update the primary UEFI image.
2. If error does not persist no additional recovery action is required.
3. If error persists, or boot is unsuccessful, replace the system board.
• I.3818002 [I.3818002]
Explanation: The firmware image capsule signature for the non-booted flash bank is invalid. Opposite
Bank CRTM Capsule Update Signature Invalid
Severity
Info

User Response
1. Update the backup UEFI image.
2. If error does not persist no additional recovery action is required.
3. If error persists, or boot is unsuccessful, replace the system board.
• I.3818003 [I.3818003]
Explanation: The CRTM flash driver could not lock the secure flash region. CRTM Could not lock secure
flash region
Severity
Info
User Response
1. If system failed to boot successfully, DC cycle the system.
2. If system boots to F1 setup, update the UEFI image and reset bank to primary (if required). If the
system boots without error, recovery is complete and no additional action is required.
3. If system fails to boot, or if the firmware update attempt fails, replace the system board.
• I.580A4 [I.580A4]
Explanation: Memory population change detected. DIMM Population Change Detected
Severity
Info
User Response
1. If you have added or removed DIMMs to the system, and no additional errors were detected,
then please ignore this message.
2. Check system event log for uncorrected DIMM failures and replace those DIMMs.
• S.2018001 [S.2018001]
Explanation: An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID for
the device is % and the Device ID is %. PCIe Uncorrected Error Detected
Severity
Error
User Response
1. If this computer node and/or any attached cables were recently installed, moved, serviced or
upgraded: a. Reseat the 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 Lenovo XClarity Essentials OneCLI Utility.
2. Check the IBM support site for an applicable device driver, firmware update, or other information
that applies to this error. Load the new device driver and install any required firmware updates.
3. If problem persists, remove the adapter. If system reboots successfully without the adapter,
replace that adapter.
4. Replace the processor.
• S.3020007 [S.3020007]
Explanation: A firmware fault has been detected in the UEFI image. Internal UEFI Firmware Fault
Detected, System halted
Appendix B. UEFI (POST) error codes 443

Severity
Error
User Response
1. Check the IBM support site for an applicable service bulletin or firmware update that applies to
this error.
2. Update the UEFI image.
3. Replace the system board.
• S.3028002 [S.3028002]
Explanation: Boot permission timeout detected. Boot Permission Negotiation Timeout
Severity
Error
User Response
1. Check CMM/IMM logs for communication errors and resolve.
2. Reseat the system
3. If problem persists contact support
• S.3030007 [S.3030007]
Severity
Error
User Response
1. Check IBM support site for an applicable service bulletin or firmware update that applies to this
error.
• S.3040007 [S.3040007]
Severity
Error
User Response
error.
• S.3050007 [S.3050007]
Severity

Error
User Response
error.
• S.3060007 [S.3060007]
Severity
Error
User Response
error.
• S.3070007 [S.3070007]
Severity
Error
User Response
error.
• S.3108007 [S.3108007]
Explanation: ] The default system settings have been restored. System Configuration Restored to
Defaults
Severity
Error
User Response
error.
• S.3818004 [S.3818004]
Explanation: The CRTM flash driver could not successfully flash the staging area. A failure occurred.
CRTM Update Failed
Severity
Error

User Response
1. Continue booting the system. If the 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 update the UEFI image.
• S.3818007 [S.3818007]
Explanation: The firmware image capsules for both flash banks could not be verified. CRTM image
capsule could not be verified
Severity
Error
User Response
1. If system failed to boot successfully, DC cycle system.
2. If system boots to F1 setup, update the UEFI image and reset bank to primary (if required). If the
system boots without error, recovery is complete and no additional action is required.
3. If system fails to boot, or if the firmware update attempt fails, replace the system board.
• S.51003 [S.51003]
Explanation: An uncorrectable memory error was detected in DIMM slot % on rank %. [S.51003] An
uncorrectable memory error was detected on processor % channel %. The failing DIMM within the
channel could not be determined. [S.51003] An uncorrectable memory error has been detected. Fatal
Memory Error Occurred
Severity
Error
User Response
1. If the compute 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: The event Log might 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 recurs on the same DIMM connector, replace the other DIMMs on the same memory
channel.
this memory error.
5. If problem recurs on the same DIMM connector, inspect connector for damage. If found, replace
the system board.
6. Replace the affected processor.
7. Replace system board.
• S.51006 [S.51006]
Explanation: A memory mismatch has been detected. Please verify that the memory configuration is
valid. One or More Mismatched DIMMs Detected
Severity

Error
User Response
1. Could follow an uncorrectable memory error or failed memory test. Check the 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.
3. Disable memory mirroring and sparing. If this action eliminates the mismatch, check the IBM
Support site for information related to this problem.
4. Update UEFI firmware.
5. Replace the DIMM.
6. Replace the processor.
• S.51009 [S.51009]
Explanation: No system memory has been detected. No Memory Detected
Severity
Error
User Response
1. If any memory errors are logged other than this one, take actions indicated for those codes first.
2. If no other memory diagnostic codes appear in the logs, verify that all DIMM connectors are
enabled using the Setup utility or Lenovo XClarity Essentials OneCLI Utility.
3. If the problem remains, shut down and remove node from chassis and physically verify that one
or more DIMMs are installed and that all DIMMs are installed in the correct population sequence.
4. If DIMMs are present and properly installed, check for any lit DIMM-connector LEDs, and if
found, reseat those DIMMs.
5. Reinstall node in chassis, power on node, then check logs for memory diagnostic codes.
6. If the problem remains, replace the processor.
7. If the problem remains, replace the system board.
• S.58008 [S.58008]
Explanation: A DIMM has failed the POST memory test. DIMM Failed Memory Test
Severity
Error
User Response
1. You must AC-cycle the system to re-enable the affected DIMM connector or re-enable manually
using the Setup utility.
2. If the compute 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: The event Log might
contain a recent 00580A4 event denoting detected change in DIMM population that could be
related to this problem.)
3. If problem persists, replace the DIMM identified by LightPath and/or event log entry.
4. If problem recurs 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. If problem
follows a moved DIMM to a different memory channel, replace that DIMM.

this memory error.
6. 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. Remove the affected processor and inspect the processor socket pins for damaged or mis-
aligned pins. If damage is found, or this is an upgrade processor, replace the system board. If
there are multiple processors, swap them to move affected processor to another processor
socket and retry. If problem follows the affected processor (or there is only one processor),
replace the affected processor.
• S.68005 [S.68005]
Explanation: An error has been detected by 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. Critical IOH-PCI Error
Severity
Error
User Response
1. Check the log for a separate error related to an associated PCIe device and resolve that error.
2. Check the IBM support site for an applicable service bulletin or firmware update for the system
or adapter that applies to this error.
• W.11004 [W.11004]
Explanation: A processor within the system has failed the BIST. Processor Self Test Failure Detected
Severity
Error
User Response
1. If the processor or firmware was just updated, check the IBM support site for an applicable
service bulletin or firmware update that applies to this processor error.
2. 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 the processor socket on each processor
removal and replace system board first if the processor socket is damaged or mis-aligned pins
are found.
• W.3818005 [W.3818005]
Explanation: The CRTM flash driver could not successfully flash the staging area. The update was
aborted CRTM Update Aborted
Severity
Warning
User Response
1. Continue booting the 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 update the UEFI image.
• W.381800D [W.381800D]
Explanation: TPM physical presence is in asserted state TPM physical presence is in asserted state
Severity
Warning
User Response
1. Complete any administrative tasks requiring the TPM physical presence switch to be in the "ON"
position.
2. Restore the physical presence switch to the "OFF" position and reboot the system.
• W.50001 [W.50001]
Explanation: A DIMM has been disabled due to an error detected during POST. DIMM Disabled
Severity
Info
User Response
1. If the DIMM was disabled because of a memory fault, follow the procedure for that event.
2. If no memory fault is recorded in the logs and no DIMM connector error LEDs are lit, re-enable
the DIMM through the Setup utility or Lenovo XClarity Essentials OneCLI Utility.
3. If the problem persists, Power cycle the compute node from the management console.
4. Reset the IMM to default settings.
5. Reset UEFI to default settings.
6. Update IMM and UEFI firmware.
• W.58001 [W.58001]
Explanation: The PFA Threshold limit (correctable error logging limit) has been exceeded on DIMM
number % at address %. MC5 Status contains % and MC5 Misc contains %. DIMM PFA Threshold
Exceeded
Severity
Error
User Response
1. If the compute 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: The event Log might contain a recent 00580A4 event denoting detected
change in DIMM population that could be related to this problem.)
2. Check the 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. If PFA follows a moved DIMM
to any DIMM connector on the different memory channel, replace the moved DIMM.
5. Check the IBM support site for an applicable Service Bulletins (Service bulletins) that applies to
this memory error. (Link to IBM support service bulletins)
6. 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. Remove the affected processor and inspect the processor socket pins for damaged or mis-
aligned pins. If damage is found or the processor is an upgrade part, replace the system board.
8. Replace affected processor.
• W.68002 [W.68002]
Explanation: A CMOS battery error has been detected CMOS Battery Fault
Severity
Error
User Response
1. If the system was recently installed, moved, or serviced, make sure the battery is properly
seated.
this error.
3. Replace the CMOS battery.

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

The following messages can result when you run the Broadcom network test.
Test results for the DSA Broadcom network test

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

The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
– Lenovo Support website
– Latest level of DSA
– Latest level of BMC/IMM
• 405-001-000 : BRCM:TestMIIRegisters Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 405-002-000 : BRCM:TestEEPROM Test Passed
The test passed.
Recoverable
No

Severity
Event
Serviceable
No
No
Related links
• 405-003-000 : BRCM:TestInternalMemory Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 405-004-000 : BRCM:TestInterrupt Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 405-005-000 : BRCM:TestLoopbackMAC Test Passed
The test passed.
Recoverable
No
Severity
Event

Serviceable
No
No
Related links
• 405-006-000 : BRCM:TestLoopbackPhysical Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 405-007-000 : BRCM:TestLEDs Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 405-800-000 : BRCM:TestControlRegisters Test Aborted
The control registers test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
Appendix C. DSA diagnostic test results 453

No
Related links
• 405-801-000 : BRCM:TestMIIRegisters Test Aborted
The MII register test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 405-802-000 : BRCM:TestEEPROM Test Aborted
The EEPROM test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 405-803-000 : BRCM:TestInternalMemory Test Aborted
The internal memory test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No

Related links
• 405-804-000 : BRCM:TestInterrupt Test Aborted
The interrupt test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 405-805-000 : BRCM:TestLoopbackMAC Test Aborted
Loopback testing at the MAC layer was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 405-806-000 : BRCM:TestLoopbackPhysical Test Aborted
Loopback testing at the physical layer was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links

• 405-807-000 : BRCM:TestLEDs Test Aborted
Verification of status LEDs was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 405-900-000 : BRCM:TestControlRegisters Test Failed
A failure was detected while testing internal MAC registers
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check component firmware level and upgrade if necessary. The installed firmware level can be
found in the DSA Diagnostic Event Log within the Firmware/VPD section for this component.
2. Rerun the test.
3. If failure remains, refer to "Troubleshooting by symptom" in the system "Installation and Service
Guide" for the next corrective action.
Related links
• 405-901-000 : BRCM:TestMIIRegisters Test Failed
A failure was detected while testing internal PHY registers.
Recoverable
No
Severity
Error
Serviceable
Yes

No
User Response
2. Rerun the test.
Related links
• 405-902-000 : BRCM:TestEEPROM Test Failed
A failure was detected while testing non-volatile RAM.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 405-903-000 : BRCM:TestInternalMemory Test Failed
A failure was detected while testing internal memory.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

2. Rerun the test.
Related links
• 405-904-000 : BRCM:TestInterrupt Test Failed
A failure was detected while testing interrupts.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 405-905-000 : BRCM:TestLoopbackMAC Test Failed
BRCM:TestLoopbackMAC Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

2. Rerun the test.
Related links
• 405-906-000 : BRCM:TestLoopbackPhysical Test Failed
A failure was detected during the loopback test at the physical layer.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 405-907-000 : BRCM:TestLEDs Test Failed
A failure was detected while verifying operation of the status LEDs.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.

Related links
DSA Brocade test results

The following messages can result when you run the Brocade test.
Test results for the DSA Brocade test

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

The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 218-001-000 : Brocade:ExternalLoopbackTest Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 218-002-000 : Brocade:SerdesLoopbackTest Passed
The test passed.
Recoverable
No
Severity

Event
Serviceable
No
No
Related links
• 218-003-000 : Brocade:PCILoopbackTest Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 218-004-000 : Brocade:ExternalEthLoopbackTest Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 218-005-000 : Brocade:SerdesEthLoopbackTest Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable

No
No
Related links
• 218-006-000 : Brocade:InternalLoopbackTest Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 218-800-000 : Brocade:MemoryTest Aborted
The test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 218-801-000 : Brocade:ExternalLoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No

No
Related links
• 218-802-000 : Brocade:SerdesLoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 218-803-000 : Brocade:PCILoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 218-804-000 : Brocade:ExternalEthLoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links

• 218-805-000 : Brocade:SerdesEthLoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 218-806-000 : Brocade:InternalLoopbackTest Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 218-900-000 : Brocade:MemoryTest Failed
A failure was detected while testing the adapter memory.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Rerun the test.

2. Verify whether the firmware is at proper level.
3. Rerun the test.
4. If the problem remains, contact your IBM technical-support representative.
Related links
• 218-901-000 : Brocade:ExternalLoopbackTest Failed
A failure was detected during the Loopback test.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check cable connections.
2. Rerun the test.
4. Rerun the test.
Related links
• 218-902-000 : Brocade:SerdesLoopbackTest Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Rerun the test.
3. Rerun the test.

Related links
• 218-903-000 : Brocade:PCILoopbackTest Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Rerun the test.
3. Rerun the test.
Related links
• 218-904-000 : Brocade:ExternalEthLoopbackTest Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check or replace SFP/cable.
2. Rerun the test.
4. Rerun the test.
Related links

• 218-905-000 : Brocade:SerdesEthLoopbackTest Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Rerun the test.
3. Rerun the test.
Related links
• 218-906-000 : Brocade:InternalLoopbackTest Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Rerun the test.
3. Rerun the test.
Related links

DSA checkpoint panel test results
The following messages can result when you run the checkpoint panel test.
Test results for the DSA checkpoint panel test

The following messages can result when you run the DSA checkpoint panel test.
• 180-000-000 : Check-point Panel Test Passed

Check-point Panel Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 180-801-000 : Check-point Panel Test Aborted
Check-point Panel Test Aborted. BMC is unable to verify that the operator information panel cable is
connected.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
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.
Related links
• 180-901-000 : Check-point Panel Test Failed

Check-point Panel Test Failed. Operator reported incorrect display.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check the operator information panel cabling for loose or broken connections at both ends or
damage to the cable.
2. Replace the information panel cable if damage is present.
4. Replace the operator information panel assembly.
Related links
DSA CPU stress test results

The following messages can result when you run the CPU stress test.
Test results for the DSA CPU stress test

The following messages can result when you run the DSA CPU stress test.
• 089-000-000 : CPU Stress Test Passed

CPU Stress Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links

• 089-801-000 : CPU Stress Test Aborted
CPU Stress Test Aborted. Internal Program Error.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
1. Turn off and restart the system.
2. Make sure that the DSA Diagnostic code is at the latest level.
4. Check system firmware level and upgrade if necessary. The installed firmware level can be found
in the DSA Diagnostic Event Log within the Firmware/VPD section for this component. The latest
level firmware for this component can be found in reference to this system type at the IBM
Support website.
6. If the system has stopped responding, turn off and restart the system and then run the test again.
Related links
CPU Stress Test Aborted. System resource unavailability error.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
in the DSA Diagnostic Event Log within the Firmware/VPD section for this component.

Related links
CPU Stress Test Aborted. Memory size is insufficient to run the test. At least 1GB is required.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
Related links
CPU Stress Test Aborted. User pressed Ctrl-C.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
Related links
• 089-901-000 : CPU Stress Test Failed
CPU Stress Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes

No
User Response
Related links
DSA Emulex adapter test results

The following messages can result when you run the Emulex adapter test.
Test results for the DSA Emulex adapter test

The following messages can result when you run the DSA Emulex adapter test.
• 516-000-000 : ELXUCNA: NIC MAC LoopBackTest Passed

The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 516-001-000 : ELXUCNA: NIC PHY LoopBackTest Passed
The test passed.
Recoverable
No
Severity
Event

Serviceable
No
No
Related links
• 516-002-000 : ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 516-800-000 : ELXUCNA: NIC MAC LoopBackTest Aborted
Loopback testing at the MAC layer was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 516-801-000 : ELXUCNA: NIC PHY LoopBackTest Aborted
Loopback testing at the physical layer was canceled.
Recoverable
No
Severity
Warning
Serviceable
No

No
Related links
• 516-802-000 : ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Aborted
Verification of status LEDs was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 516-900-000 : ELXUCNA: NIC MAC LoopBackTest Failed
A failure was detected during the loopback test at the MAC layer.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 516-901-000 : ELXUCNA: NIC PHY LoopBackTest Failed
A failure was detected during the loopback test at the physical layer.
Recoverable
No

Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 516-902-000 : ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Failed
A failure was detected while verifying operation of the status LEDs.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
DSA EXA port ping test results

The following messages can result when you run the EXA port ping test.
Test results for the DSA EXA port ping test

The following messages can result when you run the DSA EXA port ping test.

• 401-000-000 : EXA Port Ping Test Passed
EXA Port Ping Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 401-801-000 : EXA Port Ping Test Aborted
EXA Port Ping Test Aborted. Unable to get device base address.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
1. Remove power cables, wait for 45 seconds, reconnect and rerun the test.
2. Make sure that the scalability cable connections are as per specification.
3. Make sure that DSA and BIOS/uEFI are at the latest level.
4. If the problem remains, contact your technical-service representative.
Related links
• 401-802-000 : EXA Port Ping Test Aborted
EXA Port Ping Test Aborted. Port connections may not be correct.
Recoverable
No
Severity
Warning
Serviceable
Yes
No

User Response
Related links
• 401-901-001 : EXA Port Ping Test Failed
EXA Port Ping Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
3. Check scalability cables for loose connections.
4. Replace the scalability cable(s) for specified port(s).
Related links
DSA hard drive test results

The following messages can result when you run the hard drive test.
Test results for the DSA hard drive test

The following messages can result when you run the DSA hard drive test.
• 217-000-000 : HDD Test Passed

HDD Stress Test Passed.
Recoverable
No
Severity
Event

Serviceable
No
No
Related links
• 217-800-000 : HDD Test Aborted
HDD Test Aborted. The test was canceled.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
2. Rerun the test.
3. Verify that Hard drive supports self test and self test logging.
4. If the problem remains, contact your technical-support representative.
Related links
• 217-900-000 : HDD Test Failed
HDD Test Failed. The hard drive self-test detected a failure.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
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
DSA Intel network test results

The following messages can result when you run the Intel network test.
Test results for the DSA Intel network test

The following messages can result when you run the DSA Intel network test.
• 406-000-000 : IANet:Registers Test Passed

The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 406-001-000 : IANet:EEPROM Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 406-002-000 : IANet:FIFO Test Passed
The test passed.
Recoverable
No

Severity
Event
Serviceable
No
No
Related links
• 406-003-000 : IANet:Interrupts Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 406-004-000 : IANet:Loopback Test Passed
The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 406-800-000 : IANet:Registers Test Aborted
Registers test was canceled.
Recoverable
No
Severity
Warning

Serviceable
No
No
Related links
• 406-801-000 : IANet:EEPROM Test Aborted
EEPROM test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 406-802-000 : IANet:FIFO Test Aborted
FIFO test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 406-803-000 : IANet:Interrupts Test Aborted
Interrupt test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No

No
Related links
• 406-804-000 : IANet:Loopback Test Aborted
Loopback test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 406-900-000 : IANet:Registers Test Failed
A failure was detected during the Registers test.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 406-901-000 : IANet:EEPROM Test Failed
A failure was detected during the EEPROM test.
Recoverable
No

Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 406-902-000 : IANet:FIFO Test Failed
A failure was detected during the FIFO test.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Rerun the test.
Related links
• 406-903-000 : IANet:Interrupts Test Failed
A failure was detected during the Interrupt test.
Recoverable
No
Severity
Error
Serviceable

Yes
No
User Response
2. Rerun the test.
3. Check interrupt assignments in the PCI Hardware section of the DSA Diagnostic Log. If the
ethernet device is sharing interrupts, if possible modify the interrupt assignments using F1 Setup
to assign a unique interrupt to the device.
4. Rerun the test.
Related links
• 406-904-000 : IANet:Loopback Test Failed
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check the Ethernet cable for damage and ensure correct cable type and attachment.
3. Rerun the test.
Related links
DSA LSI hard drive test results

The following messages can result when you run the LSI hard drive test.

Test results for the DSA LSI hard drive test
The following messages can result when you run the DSA LSI hard drive test.
• 407-000-000 : LSIESG:DiskDefaultDiagnostic Test Passed

The test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 407-800-000 : LSIESG:DiskDefaultDiagnostic Test Aborted
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 407-900-000 : LSIESG:DiskDefaultDiagnostic Test Failed
The hard drive self-test detected a failure.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

2. Rerun the test.
3. Verify whether the firmware is at the latest level.
4. Rerun the test.
Related links
DSA Mellanox adapter test results

The following messages can result when you run the Mellanox adapter test.
Test results for the DSA Mellanox adapter test

The following messages can result when you run the DSA Mellanox adapter test.
• 408-000-000 : MLNX:MLNX_DiagnosticTestEthernetPort Test Passed

Port Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 408-001-000 : MLNX:MLNX_DiagnosticTestIBPort Test Passed
Port Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 408-800-000 : MLNX:MLNX_DiagnosticTestEthernetPort Test Aborted

Port Test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 408-801-000 : MLNX:MLNX_DiagnosticTestIBPort Test Aborted
Port Test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 408-900-000 : MLNX:MLNX_DiagnosticTestEthernetPort Test Failed
Port Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Make sure that the physical link of the port under test in the active state.
2. If these condition was met but the test keeps failing the port's adapter might be faulty.
3. Try replacing the adapter and repeating the test.
Related links

• 408-901-000 : MLNX:MLNX_DiagnosticTestIBPort Test Failed
Port Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Make sure that the physical link of the port under test in the active state and a subnet manager
running on the fabric to which the port is attached.
2. If these condition was met but the test keeps failing the port's adapter might be faulty.
3. Try replacing the adapter and repeating the test.
Related links
DSA memory isolation test results

The following messages can result when you run the memory isolation test.
Test results for the DSA memory isolation test

The following messages can result when you run the DSA memory isolation test.
• 201-000-000 : Standalone Memory Test Passed

Quick/Full Memory Test All CPUs Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links

Quick/Full Memory Test CPU 1 Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
Recoverable

No
Severity
Event
Serviceable
No
No
Related links
• 201-811-000 : Standalone Memory Test Aborted
Unable to Locate SMBIOS key "_SM_".
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
1. Perform the actions mentioned one at a time and try the test after each action.
3. Turn off the system and disconnect it from power. Wait for 45 seconds. Reseat DIMM(s).
Reconnect it to power.
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Memory test is not supported for this system.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Chipset Error: Can not turn OFF ECC error reporting in CPU.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Chipset Error: Can not disable Scubbing feature for CPU.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Program Error with Quick Memory Menu Option Selection.
Recoverable
No

Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning

Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Program Error with Full Memory Menu Option Selection.
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No

User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
The start-end address ranges in the restricted area of the memory.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Memory Upper limit is less than 16 Mbytes.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Variable range MTRR registers are larger than fixed range MTRR registers.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No

Severity
Warning
Serviceable
No
No
User Response
Related links
Invalid MTRR service request.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning

Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
Node Interleave feature must be OFF. Go to Setup and disable Node Interleave option and then re-run the
test.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
test.
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
test.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
test.
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No

User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Chipset Error: Problem in masking MSR machine check control MASK registers.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Chipset Error: Problem clearing MSR machine check control registers.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
INVALID XSECSRAT type.

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No

Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No OEM0 type 1 found.
Recoverable
No
Severity
Warning

Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No SRAT type 1 found.
Recoverable
No
Severity
Warning
Serviceable
No
No

User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No OEM1 structure found.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No IBMERROR key in OEM1 structure.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No GAS located in OEM1.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
No XSECSRAT key in OEM0 structure.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No

Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning

Serviceable
No
No
User Response
Related links
EFI-SAL Invalid parameter from GetMemoryMap function.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No

User Response
Related links
EFI/SAL: Buffer not allocated.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
EFI/SAL: Buffer allocated in GetMemoryMap too small.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

EFI/SAL Invalid parameter from GetMemoryMap function.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

CPU Doamin in ACPI not valid.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Data Mis-compare encountered.
Recoverable
No

Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning

Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Recoverable
No
Severity
Warning
Serviceable
No

No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No

User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Processor does not support MTRR register manipulation. Can not write to memory without cache.
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links

Recoverable
No
Severity
Warning
Serviceable
No
No
User Response
Related links
Memory Diagnostics Test Aborted by user.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No

Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 201-901-000 : Standalone Memory Test Failed
Memory Diagnostics Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

5. Replace any DIMMS(s) mentioned in error, one by one.
6. Make sure that all DIMMs are enabled in the Configuration/Setup Utility program.
Related links
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
Recoverable
No
Severity
Error

Serviceable
Yes
No
User Response
Related links
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links

DSA memory stress test results
The following messages can result when you run the memory stress test.
Test results for the DSA memory stress test

The following messages can result when you run the DSA memory stress test.
• 202-000-000 : MemStr Test Passed

Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 202-801-000 : MemStr Test Aborted
Internal program error.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
4. If the system has stopped responding, turn off and restart the system.
5. Check the system firmware level and upgrade if necessary.
6. Run the memory diagnostic to identify the specific failing DIMM.
7. If the failure remains, refer to "Troubleshooting by symptom" in the system "Installation and
Service Guide" for the next corrective action.
Related links

Memory size is insufficient to run the test. At least 1 GB is required.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
Related links
User pressed Ctrl-C.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
Related links
• 202-901-000 : MemStr Test Failed
Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Execute the standard DSA memory diagnostics to validate all memory.
3. Turn off the system and disconnect it from power.

4. Reseat the memory cards and DIMMs.
5. Reconnect the system to power and turn the system on.
Related links
• 202-902-000 : MemStr Test Failed
Memory size is insufficient to run the test.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Ensure that all memory is enabled by checking the "Available System Memory" in the "Resource
Utilization" section of the DSA Diagnostic Event log.
2. If necessary, access the Configuration/Setup Utility program by pressing F1 during system boot
and enable all memory.
Related links
DSA Nvidia GPU test results

The following messages can result when you run the Nvidia GPU test.
Test results for the DSA Nvidia GPU test

The following messages can result when you run the DSA Nvidia GPU test.
• 409-000-000 : NVIDIA User Diagnostic Test Passed

NVIDIA User Diagnostic test passed.

Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 409-003-000 : Nvidia::DiagnosticServiceProvider::Bandwidth Test Passed
Nvidia GPU Bandwidth test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 409-004-000 : Nvidia::DiagnosticServiceProvider::Query Test Passed
Nvidia GPU Query test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 409-005-000 : Nvidia::DiagnosticServiceProvider::Matrix Test Passed
Nvidia GPU Matrix test passed.
Recoverable
No

Severity
Event
Serviceable
No
No
Related links
• 409-006-000 : Nvidia::DiagnosticServiceProvider::Binomial Test Passed
Nvidia GPU Binomial test passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 409-800-000 : NVIDIA User Diagnostic Test Aborted
NVIDIA User Diagnostic test was canceled.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 409-803-000 : Nvidia::DiagnosticServiceProvider::Bandwidth Test Aborted
Nvidia GPU Bandwidth test was canceled.
Recoverable
No
Severity
Warning

Serviceable
No
No
Related links
• 409-804-000 : Nvidia::DiagnosticServiceProvider::Query Test Aborted
Nvidia GPU Query test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 409-805-000 : Nvidia::DiagnosticServiceProvider::Matrix Test Aborted
Nvidia GPU Matrix test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No
No
Related links
• 409-806-000 : Nvidia::DiagnosticServiceProvider::Binomial Test Aborted
Nvidia GPU Binomial test was canceled.
Recoverable
No
Severity
Warning
Serviceable
No

No
Related links
• 409-900-000 : NVIDIA User Diagnostic Test Failed
NVIDIA User Diagnostic Test Failed.
Recoverable
No
Severity
Event
Serviceable
Yes
No
User Response
1. Verify that the GPU is seated in the PCIe slot correctly by reseating the GPU. Then power cycle
the system.
2. Verify that the power connectors to the GPU are connected firmly. Then power cycle the system.
3. Run nvidia-smi -q In some cases this will report a poorly connected power cable.
4. Rerun the diagnostics, using the same GPU, on system that is known to be working. A variety of
system issues can cause diagnostic failure.
Related links
• 409-903-000 : Nvidia::DiagnosticServiceProvider::Bandwidth Test Failed
Nvidia GPU Bandwidth Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
the system.

Related links
• 409-904-000 : Nvidia::DiagnosticServiceProvider::Query Test Failed
Nvidia GPU Query Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
the system.
Related links
• 409-905-000 : Nvidia::DiagnosticServiceProvider::Matrix Test Failed
Nvidia GPU Matrix Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

the system.
Related links
• 409-906-000 : Nvidia::DiagnosticServiceProvider::Binomial Test Failed
Nvidia GPU Binomial Test Failed.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
the system.
Related links
DSA optical drive test results

The following messages can result when you run the optical drive test.
Test results for the DSA optical drive test

The following messages can result when you run the DSA optical drive test.
• 215-000-000 : Optical Drive Test Passed

Optical Drive Test Passed.
Recoverable

No
Severity
Event
Serviceable
No
No
Related links
• 215-801-000 : Optical Drive Test Aborted
Optical Drive Test Aborted. Unable to communicate with driver.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
3. Check the drive cabling for loose or broken connections at both ends or damage to the cable.
Replace the cable if damage is present.
5. Check system firmware level and upgrade if necessary.The installed firmware level can be found
Related links
Optical Drive Test Aborted. A read error was encountered.
Recoverable
No
Severity
Warning
Serviceable
Yes

No
User Response
1. Insert a new CD or DVD into the drive and wait for 15 seconds for the media to be recognized.
Rerun the test.
Related links
• 215-803-000 : Optical Drive Test Failed
Optical Drive Test Failed. Disk may be in use by the operating system.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Wait for the system activity to cease
2. Run the test again
Related links
Optical Drive Test Aborted. The media tray is open.
Recoverable
No
Severity
Warning
Serviceable
Yes
No

User Response
1. Close the media tray and wait for 15 seconds for the media to be recognized. Run the test again.
Rerun the test.
Related links
Optical Drive Test Aborted. Drive media is not detected.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Rerun the test.
Related links
• 215-902-000 : Optical Drive Test Failed
Optical Drive Test Failed. Read miscompare.
Recoverable
No
Severity
Error
Serviceable
Yes

No
User Response
Rerun the test.
Related links
Optical Drive Test Aborted. Could not access the device.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Rerun the test.
4. Check system firmware level and upgrade if necessary.The installed firmware level can be found
Related links
DSA system management test results

The following messages can result when you run the system management test.

Test results for the DSA system management test
The following messages can result when you run the DSA system management test.
• 166-000-001 : IMM I2C Test Passed

IMM I2C Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 166-801-001 : IMM I2C Test Aborted
IMM returned incorrect response length.
Recoverable
No
Severity
Warning
Serviceable
Yes
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
Test cannot be completed for unknown reason.
Recoverable
No
Severity
Warning
Serviceable
Yes

No
User Response
Related links
Node Busy. Try later.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Invalid Command.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links

Invalid Command for given LUN.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Timeout while processing command.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Out of space.
Recoverable
No
Severity
Warning
Serviceable

Yes
No
User Response
Related links
Reservation Canceled or Invalid Reservation ID.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Request data truncated.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links

Request data length invalid.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Request data field length limit exceeded.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Parameter out of range.
Recoverable
No
Severity

Warning
Serviceable
Yes
No
User Response
Related links
Cannot return number of requested data bytes.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Requested Sensor, data, or record not present.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response

Related links
Invalid data field in Request.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Command illegal for specified sensor or record type.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Command response could not be provided.
Recoverable

No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Cannot execute duplicated request.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Command response could not be provided. SDR Repository in?update mode.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response

Related links
Command response could not be provided. Device in firmware update mode.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Command response could not be provided. BMC initialization in progress.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links

Destination unavailable.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Cannot execute command. Insufficient privilege level.
Recoverable
No
Severity
Warning
Serviceable
Yes
No
User Response
Related links
Cannot execute command.
Recoverable
No
Severity
Warning
Serviceable
Yes

No
User Response
Related links
• 166-901-001 : IMM I2C Test Failed
IMM Indicates failure in RTMM bus (BUS 0).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
IMM Indicates failure in TPM bus (BUS 1).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

Related links
IMM Indicates failure in Clock bus (BUS 2).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
IMM Indicates failure in LED bus (BUS 3).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

Related links
IMM Indicates failure in Power Supply bus (BUS 4).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
IMM Indicates failure in PCIe bus (BUS 5).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

Related links
IMM Indicates failure in Optional Mezz Card bus (BUS 6).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
IMM Indicates failure in the DASD bus (BUS 7).
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links

DSA tape drive test results

The following messages can result when you run the tape drive test.
Test results for the DSA tape drive test

The following messages can result when you run the DSA tape drive test.
• 264-000-000 : Tape Test Passed

Tape Test Passed.
Recoverable
No
Severity
Event
Serviceable
No
No
Related links
• 264-901-000 : Tape Test Failed
An error was found in the tape alert log.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Clean the tape drive using the appropriate cleaning media and install new media.
3. Clear the error log.
5. Make sure that the drive firmware is at the latest level.
6. Rerun the test after upgrading to the latest firmware level.

Related links
Tape Test Failed. Media is not detected.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
Related links
Tape Test Failed. Media is not detected.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response

Related links
Tape Test Failed. Drive hardware error.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Check the tape drive cabling for loose or broken connections or damage to the cable. Replace
the cable if damage is present.
Related links
Tape Test Failed. Software error: invalid request.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
2. Check the system firmware level and upgrade if necessary. The installed firmware level can be

Related links
Tape Test Failed. Unrecognized error.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
7. Check the system firmware level and upgrade if necessary.
Related links
An error was found in the block address somewhere.
Recoverable
No
Severity
Error
Serviceable
Yes

No
User Response
Related links
An error was found in getting tape capacity.
Recoverable
No
Severity
Error
Serviceable
Yes
No
User Response
1. Make sure that medium is present.
Related links

Appendix D. Getting help and technical assistance
If you need help, service, or technical assistance or just want more information about Lenovo products, you
will find a wide variety of sources available from Lenovo to assist you.
Use this information to obtain additional information about Lenovo and Lenovo products, and determine
what to do if you experience a problem with your Lenovo system or optional device.
Note: This section includes references to IBM web sites and information about obtaining service. IBM is
Lenovo's preferred service provider for the System x, Flex System, and NeXtScale System products.
Before you call

Before you call, make sure that you have taken these steps to try to solve the problem yourself.
If you believe that you require warranty service for your Lenovo product, the service technicians will be able
to assist you more efficiently if you prepare before you call.
• Check all cables to make sure that they are connected.
• Check the power switches to make sure that the system and any optional devices are turned on.
• Check for updated software, firmware, and operating-system device drivers for your Lenovo product. The
Lenovo Warranty terms and conditions state that you, the owner of the Lenovo product, are responsible
for maintaining and updating all software and firmware for the product (unless it is covered by an
additional maintenance contract). Your service technician will request that you upgrade your software and
firmware if the problem has a documented solution within a software upgrade.
• If you have installed new hardware or software in your environment, check http://www.lenovo.com/
serverproven/ to make sure that the hardware and software is supported by your product.
• Go to http://www.lenovo.com/support to check for information to help you solve the problem.
• Gather the following information to provide to the service technician. This data will help the service
technician quickly provide a solution to your problem and ensure that you receive the level of service for
which you might have contracted.
– Hardware and Software Maintenance agreement contract numbers, if applicable
– Machine type number (Lenovo 4-digit machine identifier)
– Model number
– Serial number
– Current system UEFI and firmware levels
– Other pertinent information such as error messages and logs
• Go to http://www.ibm.com/support/ entry/portal/Open_service_request to submit an Electronic Service
Request. Submitting an Electronic Service Request will start the process of determining a solution to your
problem by making the pertinent information available to the service technicians. The IBM service
technicians can start working on your solution as soon as you have completed and submitted an
Electronic Service Request.
You can solve many problems without outside assistance by following the troubleshooting procedures that
Lenovo provides in the online help or in the Lenovo product documentation. The Lenovo product
documentation also describes the diagnostic tests that you can perform. The documentation for most
systems, operating systems, and programs contains troubleshooting procedures and explanations of error
messages and error codes. If you suspect a software problem, see the documentation for the operating
system or program.

Using the documentation
Information about your Lenovo system and preinstalled software, if any, or optional device is available in the
product documentation. That documentation can include printed documents, online documents, readme
files, and help files.
See the troubleshooting information in your system documentation for instructions for using the diagnostic
programs. The troubleshooting information or the diagnostic programs might tell you that you need
additional or updated device drivers or other software. Lenovo maintains pages on the World Wide Web
where you can get the latest technical information and download device drivers and updates. To access
these pages, go to http://www.lenovo.com/support.
Getting help and information from the World Wide Web

Up-to-date information about Lenovo products and support is available on the World Wide Web.
On the World Wide Web, up-to-date information about Lenovo systems, optional devices, services, and
support is available at http://www.lenovo.com/support. The most current version of the product
documentation is available in the following product-specific Information Centers:
• Flex System products:
http://pic.dhe.ibm.com/infocenter/ flexsys/information/index.jsp
• System x products:
http://publib.boulder.ibm.com/infocenter/ systemx/documentation/index.jsp
• NeXtScale System products:
http://pic.dhe.ibm.com/infocenter/ nxtscale/documentation/index.jsp
How to send DSA data

You can use the Enhanced Customer Data Repository to send diagnostic data to IBM.
Before you send diagnostic data to IBM, read the terms of use at http://www.ibm.com/de/support/ ecurep/
terms.html.
You can use any of the following methods to send diagnostic data:
• Standard upload:
http://www.ibm.com/de/support/ ecurep/send_http.html
• Standard upload with the system serial number:
http://www.ecurep.ibm.com/app/ upload_hw
• Secure upload:
http://www.ibm.com/de/support/ ecurep/send_http.html#secure
• Secure upload with the system serial number:
https://www.ecurep.ibm.com/ app/upload_hw
Creating a personalized support web page

You can create a personalized support web page by identifying Lenovo products that are of interest to you.

To create a personalized support web page, go to http://www.ibm.com/support/ mynotifications. From this
personalized page, you can subscribe to weekly email notifications about new technical documents, search
for information and downloads, and access various administrative services.
Software service and support

Through IBM Support Line, you can get telephone assistance, for a fee, with usage, configuration, and
software problems with your Lenovo products.
For more information about Support Line and other IBM services, see http://www.ibm.com/services or see
http://www.ibm.com/planetwide for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-
SERV (1-800-426-7378).
Hardware service and support

IBM is Lenovo's preferred service provider for the System x, Flex System and NeXtScale System products.
You can receive hardware service through your Lenovo reseller or from IBM. To locate a reseller authorized
by Lenovo to provide warranty service, go to http://www.ibm.com/partnerworld and click Business Partner
Locator. For IBM support telephone numbers, see http://www.ibm.com/planetwide. In the U.S. and Canada,
call 1-800-IBM-SERV (1-800-426-7378).
In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the U.
K., these services are available Monday through Friday, from 9 a.m. to 6 p.m.
Taiwan product service

Use this information to contact product service for Taiwan.
Appendix D. Getting help and technical assistance 591

Appendix E. Notices
Lenovo may not offer the products, services, or features discussed in this document in all countries. Consult
your local Lenovo representative for information on the products and services currently available in your
area.
Any reference to a Lenovo product, program, or service is not intended to state or imply that only that
Lenovo product, program, or service may be used. Any functionally equivalent product, program, or service
that does not infringe any Lenovo intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any other product, program, or service.
Lenovo 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:
Lenovo (United States), Inc.
1009 Think Place - Building One
Morrisville, NC 27560
U.S.A.
Attention: Lenovo Director of Licensing
LENOVO 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 jurisdictions 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. Lenovo may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
The products described in this document are not intended for use in implantation or other life support
applications where malfunction may result in injury or death to persons. The information contained in this
document does not affect or change Lenovo product specifications or warranties. Nothing in this document
shall operate as an express or implied license or indemnity under the intellectual property rights of Lenovo or
third parties. All information contained in this document was obtained in specific environments and is
presented as an illustration. The result obtained in other operating environments may vary.
Lenovo may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Any references in this publication to non-Lenovo Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this Lenovo product, and use of those Web sites is at your own risk.
Any performance data contained herein was determined in a controlled environment. Therefore, the result
obtained in other operating environments may vary significantly. Some measurements may have been made
on development-level systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.

Trademarks
LENOVO, FLEX SYSTEM, SYSTEM X, NEXTSCALE SYSTEM, and X ARCHITECTURE are trademarks of
Lenovo.
Intel and Intel Xeon are trademarks of Intel Corporation in the United States, other countries, or both.
Internet Explorer, Microsoft, and Windows are trademarks of the Microsoft group of companies.
Linux is a registered trademark of Linus Torvalds.
All other trademarks are the property of their respective owners. © 2018 Lenovo
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 1 024 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
Lenovo.
Maximum memory might require replacement of the standard memory with an optional memory module.
Each solid-state memory cell has an intrinsic, finite number of write cycles that the cell can incur. Therefore, a
solid-state device has a maximum number of write cycles that it can be subjected to, expressed as total
bytes written (TBW). A device that has exceeded this limit might fail to respond to system-generated
commands or might be incapable of being written to. Lenovo 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.
Lenovo makes no representations or warranties with respect to non-Lenovo products. Support (if any) for the
non-Lenovo products is provided by the third party, not Lenovo.
Some software might differ from its retail version (if available) and might not include user manuals or all
program functionality.
Recycling information
Lenovo encourages owners of information technology (IT) equipment to responsibly recycle their equipment
when it is no longer needed. Lenovo offers a variety of programs and services to assist equipment owners in
recycling their IT products. For information on recycling Lenovo products, go to:http://www.lenovo.com/
recycling.

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 Lenovo determines that the levels of particulates or gases in your environment have
caused damage to the device, Lenovo 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 31. Limits for particulates and gases
Contaminant Limits
Particulate
• The room air must be continuously filtered with 40% atmospheric dust spot efficiency (MERV
9) according to ASHRAE Standard 52.21.
• 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.
• The deliquescent relative humidity of the particulate contamination must be more than 60%2.
• The room must be free of conductive contamination such as zinc whiskers.
Gaseous
• Copper: Class G1 as per ANSI/ISA 71.04-19853
• Silver: Corrosion rate of less than 300 Å in 30 days
1ASHRAE 52.2-2008 - Method of Testing General Ventilation Air-Cleaning Devices for Removal Efficiency by
Particle Size. Atlanta: American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc.
2The deliquescent relative humidity of particulate contamination is the relative humidity at which the dust absorbs
enough water to become wet and promote ionic conduction.
3ANSI/ISA-71.04-1985. Environmental conditions for process measurement and control systems: Airborne
contaminants. Instrument Society of America, Research Triangle Park, North Carolina, U.S.A.
Telecommunication regulatory statement

This product may not be certified in your country for connection by any means whatsoever to interfaces of
public telecommunications networks. Further certification may be required by law prior to making any such
connection. Contact a Lenovo representative or reseller for any questions.
Electronic emission notices

When you attach a monitor to the equipment, you must use the designated monitor cable and any
interference suppression devices that are supplied with the monitor.
Appendix E. Notices 595

Federal Communications Commission (FCC) statement
The following information refers to the Lenovo ThinkServer machine types 70LU, 70LV, 70LW, 70LX, 70UA,
70UB, 70UC, and 70UD.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to
Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates, uses,
and can radiate radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits.
Lenovo is not responsible for any radio or television interference caused by using other than specified or
recommended cables and connectors or by unauthorized changes or modifications to this equipment.
Unauthorized changes or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1)
this device may not cause harmful interference, and (2) this device must accept any interference received,
including interference that may cause undesired operation.
Responsible Party:
Lenovo (United States) Incorporated
7001 Development Drive
Morrisville, NC 27560
U.S.A.
Email: [email protected]
Industry Canada Class A emission compliance statement

This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Australia and New Zealand Class A statement

Attention: This is a Class A product. In a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
European Union EMC Directive conformance statement

This product is in conformity with the protection requirements of EU Council Directive 2014/30/EU on the
approximation of the laws of the Member States relating to electromagnetic compatibility. Lenovo cannot
accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended
modification of the product, including the installation of option cards from other manufacturers.
This product has been tested and found to comply with the limits for Class A equipment according to
European Standards harmonized in the Directives in compliance. The limits for Class A equipment were

derived for commercial and industrial environments to provide reasonable protection against interference
with licensed communication equipment.
Lenovo, Einsteinova 21, 851 01 Bratislava, Slovakia
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
Germany Class A statement

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur
Elektromagnetischen Verträglichkeit
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur

Elektromagnetischen Verträglichkeit Dieses Produkt entspricht den Schutzanforderungen der EU-
Richtlinie 2014/30/EU zur Angleichung der Rechtsvorschriften über die elektromagnetische Verträglichkeit in
den EU-Mitgliedsstaaten und hält die Grenzwerte der Klasse A der Norm gemäß Richtlinie.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu
betreiben. Des Weiteren dürfen auch nur von der Lenovo empfohlene Kabel angeschlossen werden. Lenovo
übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne
Zustimmung der Lenovo verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der Lenovo gesteckt/eingebaut werden.
Deutschland:
Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Betriebsmittein Dieses
Produkt entspricht dem „Gesetz über die elektromagnetische Verträglichkeit von Betriebsmitteln“ EMVG
(früher „Gesetz über die elektromagnetische Verträglichkeit von Geräten“). Dies ist die Umsetzung der EU-
Richtlinie 2014/30/EU in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit

von Betriebsmitteln, EMVG vom 20. Juli 2007 (früher Gesetz über die elektromagnetische
Verträglichkeit von Geräten), bzw. der EMV EU Richtlinie 2014/30/EU, für Geräte der Klasse A.
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen -
CE - zu führen. Verantwortlich für die Konformitätserklärung nach Paragraf 5 des EMVG ist die Lenovo
(Deutschland) GmbH, Meitnerstr. 9, D-70563 Stuttgart.
Informationen in Hinsicht EMVG Paragraf 4 Abs. (1) 4: Das Gerät erfüllt die Schutzanforderungen nach EN
55024 und EN 55032 Klasse A.
Nach der EN 55032: „Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich
Funkstörungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Maßnahmen
durchzuführen und dafür aufzukommen.“
Nach dem EMVG: „Geräte dürfen an Orten, für die sie nicht ausreichend entstört sind, nur mit besonderer
Genehmigung des Bundesministers für Post und Telekommunikation oder des Bundesamtes für Post und
Telekommunikation betrieben werden. Die Genehmigung wird erteilt, wenn keine elektromagnetischen
Störungen zu erwarten sind.“ (Auszug aus dem EMVG, Paragraph 3, Abs. 4). Dieses Genehmigungsverfahren
ist nach Paragraph 9 EMVG in Verbindung mit der entsprechenden Kostenverordnung (Amtsblatt 14/93)
kostenpflichtig.

Anmerkung: Um die Einhaltung des EMVG sicherzustellen sind die Geräte, wie in den Handbüchern
angegeben, zu installieren und zu betreiben.
Japanese electromagnetic compatibility statements
Japan VCCI Class A statement
Japanese Electrical Appliance and Material Safety Law statement (for detachable AC power cord)
JEITA harmonics guideline - Japanese Statement for AC power consumption (W)
JEITA harmonics guideline - Japanese Statement of Compliance for Products Less than or Equal to
20A per phase
JEITA harmonics guideline - Japanese Statement of Compliance for Products More than 20A
Korea Communications Commission (KCC) statement

This is electromagnetic wave compatibility equipment for business (Type A). Sellers and users need to pay
attention to it. This is for any areas other than home.
Russia Electromagnetic Interference (EMI) Class A statement
People's Republic of China Class A electronic emission statement
Taiwan Class A compliance statement

Taiwan BSMI RoHS declaration

Index
2.5-inch hot-swap hard-disk-drive backplane, install 138 power 159
2.5-inch hot-swap hard-disk-drive backplane, remove 138 ServeRAID SAS/SATA controller, fixed power supply
2.5-inch simple-swap hard-disk-drive backplate model 162, 164
assembly, install 140 ServeRAID SAS/SATA controller, hot-swap power supply
2.5-inch simple-swap hard-disk-drive backplate model 166
assembly, remove 139 ServeRAID SAS/SATA controller, redundant power supply
240 VA power distribution board cover model 168
remove 150 cache 4
3.5-inch hot-swap hard-disk-drive backplane, install 142 call home feature
3.5-inch hot-swap hard-disk-drive backplane, remove 141 Electronic Service Agent 60
3.5-inch simple-swap hard-disk-drive backplate call home tools 60
assembly, install 143 Canada Class A electronic emission statement 596
3.5-inch simple-swap hard-disk-drive backplate caution notices 1
assembly, remove 143 check log LED 15
checkout procedure 50
performing 50
China Class A electronic emission statement 599
A Class A electronic emission notice 596
coin-cell battery
ABR, automatic boot recovery 77
install 129
ac power LED 17
remove 128
acoustical noise emissions 4
collecting data 47
adapter, install 114
completing
adapter, remove 114
parts replacement 170
administrator
Component locations 15
password 34
Component locations 15
air baffle, install 96
components
air baffle, remove 95
server 19, 79
applying current firmware
configuration
using best practices 93
information 25
ASM event log 8, 57
instructions 25
assertion event, system-event log 56
Nx-boot failure 77
assistance, getting 589
ServerGuide Setup and Installation CD 25
attention notices 1
Setup Utility 25
Australia Class A statement 596
configuration programs 26
automatic boot recovery (ABR) 77
Configure BIOS for onboard SATA RAID 43
availability, server 11
configuring
Ethernet controller 38
RAID arrays 39
B with ServerGuide 28
configuring hardware 26
backup firmware configuring your server 25
starting 34 connector
bays 4 USB 15
before you install a legacy operating system 28 connectors 21
best practices Ethernet 17
use to apply current firmware and device-driver updates 93 front of server 15
bezel, remove 97 on the rear of the server 17
blue screen capture features 8 power supply 17
blue-screen capture feature rear 17
overview 8, 36 serial 17
blue-screen feature 36 USB 17
Boot Manager 34 video 17
Boot Manager program 26 contamination, particulate and gaseous 4, 595
Business Partners instructions 93, 171 controls and LEDs
button, presence detection 18 on the operator information panel 18
cooling 8
cover, install 95
cover, remove 94
C CPLD heartbeat
cable LED 55
internal routing 157 creating a personalized support web page 590
cable connection custom support web page 590
onboard RAID 160
cable routing
operating temperature enhancement kit
operator information panel 159
158 D
optical 157 danger notices 1

data collection 47 optional devices 69
dc power LED 17 power 70
deassertion event, system-event log 56 serial port 71
devices, static-sensitive ServerGuide 71
handling guidelines 94 software 72
diagnostic USB connector 72
on-board programs, starting 59 USB-device 65
tools, overview 51 errors
diagnostics format, DSA code 60
program overview 58 Ethernet 8, 17
diagnostics program controller 73
DSA Preboot 8 link status LED 17
dimensions 4 Ethernet activity
dimm LED 17–18
install 102 Ethernet connector 17
unbuffered 103 Ethernet controller configuration 26
DIMM, install 104 Ethernet controller, configure 38
DIMMs Ethernet support 8
removal 101 European Union EMC Directive conformance statement 596
display problems 67 event log 56
documentation viewing 56
using 590 event log, POST 56
documentation, updated event log, system 56
finding 1 event logs
drive 4 clearing 57
DSA 171 event logs, methods for viewing 57
edition 58 events, IMM2.1 173
program, overview 58 expansion bays 4
test log, viewing 60
text message format 60
DSA data
how to send to Lenovo 171 F
DSA log 8, 56
fan
DSA Preboot 51, 58
simple-swap 4
DSA Preboot diagnostic program 8
fan, install 128
DSA, sending data 590
fan, remove 127
DVD
fans 8
drive activity LED 15
FCC Class A notice 596
drive DVD LED 15
features 4
eject button 15
ServerGuide 28
Dynamic System Analysis 171
features, remote presence and blue-screen 8
Dynamic System Analysis (DSA) Preboot diagnostics
finding
program 8
updated documentation 1
firmware updates 3
firmware updates best practices 93
E firmware, server, recovering 76
firmware, updating 25
electrical equipment, servicing vii fixed power supply
electrical input 4 remove 131
electronic emission Class A notice 596 fixed power supply, install 132
Electronic Service Agent 60 flash power module
embedded hypervisor install 118
using 38 remove 118
enabling flash power module holder
Features on Demand install 101
Ethernet software 38 remove 100
environment 4 front I/O assembly, install 123
error codes and messages front I/O assembly, remove 122
IMM2.1 173 front view
UEFI (POST) 441 connectors 15
error messages 60 LED location 15
error messages, IMM2.1 173 front view of the server 15
error symptoms 67
general 61
hard disk drive 62
hypervisor flash device 64 G
intermittent 65
gaseous contamination 4, 595
keyboard 65
general
memory 65
problems 61
monitor 67
Germany Class A statement 597
mouse 65
grease, thermal 149
network connection 68
guidelines
operating system boot 69
servicing electrical equipment vii
optical drive 62
system reliability 93

trained service technicians vi operating temperature enhancement kit cable 125
operator information panel 123
optical drive 112
PCI riser-card bracket 137
H power distribution board 153
power distribution board cover 151
handling static-sensitive devices 94
RAID adapter battery 118
hard disk drive
RAID adapter battery holder 101
activity LED 15
second microprocessor 147
problems 62
security bezel 97
status LED 15
server components 94
hardware service and support telephone numbers 591
ServeRAID SAS/SATA controller memory module 117
hardware, configuring 26
simple-swap hard disk drive 109
head output 4
structural parts 94
heat sink, install 147
system board 155
heat sink, remove 145
the PCI riser-card assembly 99
help
Tier 1 CRUs 101
from the World Wide Web 590
usb cable 123
from World Wide Web 590
instructions for Business Partners 93, 171
sending diagnostic data 590
integrated baseboard management controller 12
sources of 589
integrated functions 4
hot-swap hard disk drive
integrated management module
install 106
event log 8
remove 105
overview 8
hot-swap power supply
Integrated Management Module 2.1 (IMM2.1)
remove 133
using 35
hot-swap power supply, install 135
integrated management module II
how to send DSA data to Lenovo 171
event log 56–57
humidity 4
programs 26
hypervisor flash device
intermittent
problems 64
problems 65
hypervisor flash device, install 121
internal cable routing 157
hypervisor flash device, removal 120
introduction 3
IP address for the IMM2.1 37
IPMI event log 8, 56–57
I IPMItool 57
IMM2 26
IMM2 heartbeat
LED 55 J
IMM2.1 error messages 173
Japanese electromagnetic compatibility statements 598
IMM2.1 events 173
jumper
IMM2.1 host name 36
UEFI boot recovery 76
IMM2.1 Web interface 37
jumpers
important notices 1, 594
system board 21
in-band
automated boot recovery method 77
manual recovery method 76
information center 590
inspecting for unsafe conditions vi
K
installation 3 Korea Class A electronic emission statement 598
installing
2.5-inch hot-swap hard-disk-drive backplane 138
2.5-inch simple-swap hard-disk-drive backplate
assembly 140 L
3.5-inch hot-swap hard-disk-drive backplane 142
LED
3.5-inch simple-swap hard-disk-drive backplate
ac power 17
assembly 143
CPLD heartbeat 55
adapter 114
dc power 17
air baffle 96
DVD drive activity 15
coin-cell battery 129
Ethernet activity 17–18
cover 95
Ethernet-link status 17
dimm 102
hard disk drive activity 15
DIMM 104
hard disk drive status 15
fan 128
IMM2 heartbeat 55
fixed power supply 132
power supply error 17
flash power module 118
power-on 18
flash power module holder 101
system information 18
front I/O assembly 123
system locator 18
heat sink 147
system pulse 55
hot-swap hard disk drive 106
system-error 18
hot-swap power supply 135
LEDs
hypervisor flash device 121
front of server 15
memory 102
light path diagnostics 53
operating temperature enhancement kit 125

power-supply 53–54 operating temperature enhancement kit cable, remove 124
on the system board 23 operating temperature enhancement kit, install 125
operator information panel 18, 53 operating temperature enhancement kit, remove 124
power-supply 53–54 operating-system event log 8, 56–57
power-supply detected problems 53–54 operator information panel
legacy operating system cable routing 159
requirement 28 controls and LEDs 18
Lenovo XClarity Administrator LEDs 18, 53
updating 39 operator information panel cable routing 159
Lenovo XClarity Essentials 39 operator information panel, install 123
Lenovo XClarity Essentials OneCLI log 57 operator information panel, remove 122
Lenovo, next generation technology 8 optical
light path diagnostics 53 cable routing 157
panel 53 optical cable routing 157
light path diagnostics, viewing without power 53 optical drive
local area network (LAN) 8 problems 62
locator LED 15 optical drive, install 112
logging 37 optical drive, remove 110
LXCE OneCLI 51 optional device problems 69
out-of-band 77
M
management, system 8
P
memory 8 particulate contamination 4, 595
install 102 parts listing 79
specifications 4 parts replacement, completing 170
UDIMM 102 parts, structural 90
unbuffered 103 password 33
memory module administrator 33
removing 101 power-on 33
memory support 8 password, power-on
menu choices switch on system board 33
Setup Utility 29 PCI
messages, error slot 1 17
POST 441 slot 2 17
method 77 PCI expansion slots 4
methods, viewing event logs 57 PCI riser card, remove 136
microprocessor 8 PCI riser-card assembly, remove 98
specifications 4 PCI riser-card bracket, remove 137
model name People's Republic of China Class A electronic emission
location 74 statement 599
policy option 34
POST
error codes 441
N event log 56
POST event log 56
New Zealand Class A statement 596
POST, intro 58
next generation technology 8
power 34
NMI button 17
cable routing 159
noise emissions 4
power-control button 15
NOS installation
requirement 4
with ServerGuide 28
specifications 4
without ServerGuide 29
supply 4
notes 1
power cable routing 159
notes, important 594
power cords 90
notices 1, 593
power distribution board cover
electronic emission 596
installing 151
FCC, Class A 596
power distribution board, install 153
Nx-boot failure 77
power distribution board, remove 152
power features
of the server 12
O power on and working inside the server 93
power problems 70, 72
obtaining 36–37 power supplies
onboard RAID redundancy support 8
cable connection 160 power supply 4
onboard RAID signal cable connection 160 power-control button 15
online documentation 3 power-on LED 12, 18
online publications 1 power-on self-test 58
operating temperature enhancement kit power-supply
cable routing 158 LEDs 53–54
operating temperature enhancement kit cable routing 158 LEDs and detected problems 53–54
operating temperature enhancement kit cable, install 125 power-supply LEDs 53–54

Preboot, DSA diagnostics program 8 hot-swap hard disk drive 105
presence detection button 18 hot-swap power supply 133
problems 67 hypervisor flash device 120
Ethernet controller 73 memory modules 101
general 61 operating temperature enhancement kit 124
hard disk drive 62 operating temperature enhancement kit cable 124
hypervisor flash device 64 operator information panel 122
intermittent 65 optical drive 110
keyboard 65 PCI riser card 136
memory 65 PCI riser-card assembly 98
monitor 67 power distribution board 152
mouse 65 power distribution board cover 150
network connection 68 RAID adapter battery 118
operating system boot 69 second microprocessor 145
optical drive 62 server components 93–94
optional devices 69 ServeRAID SAS/SATA controller memory module 116
power 70, 72 simple-swap hard disk drive 108
serial port 71 system board 154
ServerGuide 71 Tier 1 CRUs 101
software 72 usb cable 122
undetermined 74 removing and installing
USB connector 72 removing
procedure, checkout 50 structural parts 94
product service, Taiwan 591 server components 94
structural parts 94
Tier 1 CRUs 101
removing, DIMMs 101
R Replaceable server components 79
replacing
RAID adapter
server components 93
battery holder
Tier 2 CRUs 145
install 101
reset button 15
remote battery
returning
install 118
component 171
remove 118
device 171
RAID adapter battery
Russia Class A electronic emission statement 599
install 118
remove 118
RAID adapter battery holder
install 101
RAID arrays
S
configuring 39 safety v
RAS features, server 11 Safety Information 1
rear view 17 safety statements v, viii
of the server 17 second microprocessor, install 147
recovering the server firmware 76 second microprocessor, remove 145
redundancy support security bezel, install 97
power supplies 8 sending diagnostic data 590
redundant 8 sending DSA data
cooling 8 to Lenovo 171
Ethernet connection 8 serial connector 17
Redundant serial number
Ethernet capabilities 11 location 74
hot-swap power supplies 11 serial port problems 71
reliability, server 11 server
remote presence feature offerings 8
using 36 power features 12
removing turn off 12
2.5-inch hot-swap hard-disk-drive backplane 138 turn on 12
2.5-inch simple-swap hard-disk-drive backplate working inside with the power on 93
assembly 139 server , backup firmware
3.5-inch hot-swap hard-disk-drive backplane 141 starting 34
3.5-inch simple-swap hard-disk-drive backplate server components 19, 79
assembly 143 server firmware, recovering 76
adapter 114 server rear view 17
air baffle 95 server shutdown 12
bezel 97 server, front view 15
coin-cell battery 128 ServeRAID SAS/SATA controller cable routing, fixed
cover 94 power supply model 162, 164
fan 127 ServeRAID SAS/SATA controller cable routing, hot-swap
fixed power supply 131 power supply model 166
flash power module 118 ServeRAID SAS/SATA controller cable routing, redundant
flash power module holder 100 power supply model 168
front I/O assembly 122 ServeRAID SAS/SATA controller memory module, install 117
heat sink 145 ServeRAID SAS/SATA controller memory module, remove 116

ServeRAID SAS/SATA controller, fixed power supply model telecommunication regulatory statement 595
cable routing 162, 164 telephone numbers 591
ServeRAID SAS/SATA controller, hot-swap power supply model temperature 4
cable routing 166 test log, viewing 60
ServeRAID SAS/SATA controller, redundant power supply model the PCI riser-card assembly, install 99
cable routing 168 thermal grease 149
ServeRAID support 8 Tier 1 CRUs, install 101
ServerGuide Tier 2 CRUs, replacement 145
features 28 TOE 4
NOS installation 28 tools, call home 60
setup 28 tools, diagnostic 51
Setup and Installation CD 25 TPM switch block description 21
using 27 trademarks 594
ServerGuide CD 8 trained service technicians, guidelines vi
service and support troubleshooting 47
before you call 589 symptom 61
hardware 591 turning off the server 12
software 591 integrated baseboard management controller 12
service bulletins 49 turning on the server 12
serviceability, server 11
servicing electrical equipment vii
Setup Utility 25–26
menu choices 29 U
starting 29
UDIMM
using 29
considerations 103
shutting down the server 12
requirement 102–103
simple-swap hard disk drive
UEFI
install 109
boot recovery jumper 76
remove 108
error codes 441
size 4
unbuffered
slots
dimm 103
PCI expansion 4
memory 103
software problems 72
Unbuffered DIMM 102–103
software service and support telephone numbers 591
undetermined problems 74
specifications 4
undocumented problems 49
standby mode 12
United States FCC Class A notice 596
starting
Universal Serial Bus (USB) problems 72
Setup Utility 29
unsafe conditions, inspecting for vi
the backup firmware 34
UpdateXpress 25
static-sensitive devices
updating
handling guidelines 94
DMI/SMBIOS 41
structural parts 90
firmware 25
support web page, custom 590
Lenovo XClarity Administrator 39
switch block 21
Universal Unique Identifier (UUID) 40
switches
USB
system board 21
connector 15, 17
system
usb cable, install 123
error LED front 18
usb cable, remove 122
information LED 18
using
locator LED, front 18
embedded hypervisor 38
system board
Setup Utility 29
connectors 21
the remote presence feature 36
LEDs 23
using best practices
power-on password switch 33
to apply firmware and device-driver updates 93
switches and jumpers 21
usingIntegrated Management Module 2.1 (IMM2.1) 35
system board internal connectors 21
utility, Setup 26
system board, install 155
starting 29
system board, remove 154
using 29
system event log 56
system pulse LEDs 55
system reliability guidelines 93
system-error LED 15
system-event log 56
V
system-event log, assertion event 56 VGA connector
system-event log, deassertion event 56 rear 17
Systems Director 8 video controller, integrated
systems management 8 specifications 4
viewing event log 57
VMware Hypervisor support 26
T
Taiwan BSMI RoHS declaration 600
Taiwan Class A electronic emission statement 599
W
Taiwan product service 591 Wake on LAN feature 12

weight 4 X
what the server offers 8
working inside with the power on 93 x3250
introduction 3


PDF 3633 Isg

Uploaded by

Copyright:

Available Formats

PDF 3633 Isg

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDF 3633 Isg

Uploaded by

Copyright:

Available Formats

Lenovo System x3250 M6

Installation and Service Guide

Machine Types: 3633 and 3943

Eighth Edition (July 2018)

© Copyright Lenovo 2016, 2018.

Safety . . . . . . . . . . . . . . . . . . v Accessing RAID configuration utility . . . . . 39

© Copyright Lenovo 2016, 2018 i

ii Lenovo System x3250 M6 Installation and Service Guide

© Copyright Lenovo 2016, 2018 iii

Antes de instalar este produto, leia as Informações de Segurança.

Læs sikkerhedsforskrifterne, før du installerer dette produkt.

Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.

Avant d'installer ce produit, lisez les consignes de sécurité.

Vor der Installation dieses Produkts die Sicherheitshinweise lesen.

Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.

Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.

Antes de instalar este produto, leia as Informações sobre Segurança.

© Copyright Lenovo 2016, 2018 v

Läs säkerhetsinformationen innan du installerar den här produkten.

Guidelines for trained service technicians

Inspecting for unsafe conditions

vi Lenovo System x3250 M6 Installation and Service Guide

Guidelines for servicing electrical equipment

© Copyright Lenovo 2016, 2018 vii

Electrical current from power, telephone, and communication cables is hazardous.

To avoid a shock hazard:

1. Turn everything OFF. 1. Turn everything OFF.

viii Lenovo System x3250 M6 Installation and Service Guide

Dispose of the battery as required by local ordinances or regulations.

© Copyright Lenovo 2016, 2018 ix

CAUTION: Use safe practices when lifting.

≥ 18 kg (39.7 lb) ≥ 32 kg (70.5 lb) ≥ 55 kg (121.2 lb)

x Lenovo System x3250 M6 Installation and Service Guide

© Copyright Lenovo 2016, 2018 xi

Rack Safety Information, Statement 2

• Always lower the leveling pads on the rack cabinet.

xii Lenovo System x3250 M6 Installation and Service Guide

For safety information, warranties, licenses, and product documentation, go to:

For warranty lookup (type, duration, status), go to:

Notices in this document

The following notices and notices are used in this document:

• Note: These notices provide important tips, guidance, or advice.

© Copyright Lenovo 2016, 2018 1

For a list of supported optional devices for the server, go to:

Record information about the server in the following table.

Table 1. Record of the system information

Product name Machine types Model number Serial number

Figure 1. ID label on the front of the server

© Copyright Lenovo 2016, 2018 3

Warranty and service information

Technologies and software information

Server features and specifications

Microprocessor (depending on the model):

4 Lenovo System x3250 M6 Installation and Service Guide

For a list of supported microprocessors, go to:

Chapter 2. About the Lenovo System x3250 M6 server 5

ServeRAID C110 capabilities that support RAID levels 0, 1, 5, and 10

6 Lenovo System x3250 M6 Installation and Service Guide

Chapter 2. About the Lenovo System x3250 M6 server 7