IBM 8835, Eserver 325 Type 8835 Maintenance And Troubleshooting Manual
ERserver
Eserver 325 Type 8835
Hardware Maintenance Manual and Troubleshooting
Guide
ER s e r v e r
Eserver 325 Type 8835
Hardware Maintenance Manual and Troubleshooting
Guide
Before using this information and the product it supports, read Appendix C, “Notices,” on page 143.
The most recent version of this document is available at http://www.ibm.com/pc/support/.
Fifth Edition (November 2004)
© Copyright International Business Machines Corporation 2002, 2003. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
About this manual
This manual contains diagnostic information, a Symptom-to-FRU index, service
information, error codes, error messages, and configuration information for the IBM
Eserver
™
325 Type 8835 server.
Important: This manual is intended for trained servicers who are familiar with IBM
Eserver
review “Safety information” on page 101.
Important safety information
Be sure to read all caution and danger statements in this book before performing
any of the instructions.
Leia todas as instruções de cuidado e perigo antes de executar qualquer operação.
Prenez connaissance de toutes les consignes de type Attention et
Danger avant de procéder aux opérations décrites par les instructions.
Lesen Sie alle Sicherheitshinweise, bevor Sie eine Anweisung ausführen.
®
products. Before servicing an IBM product, be sure to
®
Online support
Accertarsi di leggere tutti gli avvisi di attenzione e di pericolo prima di effettuare
qualsiasi operazione.
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a
cabo cualquier operación.
WARNING: Handling the cord on this product or cords associated with accessories
sold with this product, will expose you to lead, a chemical known to the State of
California to cause cancer, and birth defects or other reproductive harm. Wash
hands after handling.
ADVERTENCIA: El contacto con el cable de este producto o con cables de
accesorios que se venden junto con este producto, pueden exponerle al plomo, un
elemento químico que en el estado de California de los Estados Unidos está
considerado como un causante de cancer y de defectos congénitos, además de
otros riesgos reproductivos. Lávese las manos después de usar el producto.
You can download the most current diagnostic, BIOS flash, and device-driver files
from http://www.ibm.com/pc/support/.
© Copyright IBM Corp. 2002, 2003 iii
iv Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Contents
About this manual . . . . . . . . . . . . . . . . . . . . . . . iii
Important safety information . . . . . . . . . . . . . . . . . . . . iii
Online support . . . . . . . . . . . . . . . . . . . . . . . . . iii
Chapter 1. General information . . . . . . . . . . . . . . . . . . .1
Related publications . . . . . . . . . . . . . . . . . . . . . . .2
Notices and statements used in this book . . . . . . . . . . . . . . .2
Features and specifications . . . . . . . . . . . . . . . . . . . . .3
Server controls, LEDs, and power . . . . . . . . . . . . . . . . . .4
Front view . . . . . . . . . . . . . . . . . . . . . . . . . .4
Rear view . . . . . . . . . . . . . . . . . . . . . . . . . .5
Server power features . . . . . . . . . . . . . . . . . . . . . .6
Turning on the server . . . . . . . . . . . . . . . . . . . . .6
Turning off the server . . . . . . . . . . . . . . . . . . . . .7
Chapter 2. Configuration . . . . . . . . . . . . . . . . . . . . .9
Using the Configuration/Setup Utility program . . . . . . . . . . . . . .9
Starting the Configuration/Setup Utility program . . . . . . . . . . . .10
Using the RAID configuration programs . . . . . . . . . . . . . . . .10
Configuring the Gigabit Ethernet controllers . . . . . . . . . . . . . .10
Using the baseboard management controller firmware update utility program 11
Chapter 3. Diagnostics . . . . . . . . . . . . . . . . . . . . .13
General checkout . . . . . . . . . . . . . . . . . . . . . . . .13
Checkout procedure . . . . . . . . . . . . . . . . . . . . . .14
Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . .15
Power-on self-test . . . . . . . . . . . . . . . . . . . . . . . .15
POST beep codes . . . . . . . . . . . . . . . . . . . . . .15
POST error messages . . . . . . . . . . . . . . . . . . . . .16
Diagnostic programs and error messages . . . . . . . . . . . . . . .16
Text messages . . . . . . . . . . . . . . . . . . . . . . . .17
Downloading the diagnostics program . . . . . . . . . . . . . . .17
Starting the diagnostic programs and viewing the test log . . . . . . . .18
Using the diagnostics CD . . . . . . . . . . . . . . . . . . .18
Using the diagnostic diskette . . . . . . . . . . . . . . . . . .18
Diagnostic error message tables . . . . . . . . . . . . . . . . .19
Error charts . . . . . . . . . . . . . . . . . . . . . . . . . .19
Small computer system interface (SCSI) messages (some models) . . . . .19
Error LEDs . . . . . . . . . . . . . . . . . . . . . . . . . .20
Updating BIOS code . . . . . . . . . . . . . . . . . . . . . . .21
Recovering from a POST/BIOS update failure . . . . . . . . . . . .21
Erasing a lost or forgotten password . . . . . . . . . . . . . . . . .22
Clearing CMOS memory . . . . . . . . . . . . . . . . . . . .23
Power checkout . . . . . . . . . . . . . . . . . . . . . . . .24
Chapter 4. Installing options . . . . . . . . . . . . . . . . . . .25
Installation guidelines . . . . . . . . . . . . . . . . . . . . . .25
System reliability guidelines . . . . . . . . . . . . . . . . . . .25
Handling static-sensitive devices . . . . . . . . . . . . . . . . .25
Major components of the Eserver 325 Type 8835 server . . . . . . . . .26
Removing the cover and bezel . . . . . . . . . . . . . . . . . . .27
Working with adapters . . . . . . . . . . . . . . . . . . . . . .28
Installing an adapter . . . . . . . . . . . . . . . . . . . . . . .31
© Copyright IBM Corp. 2002, 2003 v
Working with a hard disk drive . . . . . . . . . . . . . . . . . . .34
Installing a hot-swap hard disk drive . . . . . . . . . . . . . . . .35
Installing a non-hot-swap hard disk drive . . . . . . . . . . . . . .36
Installing memory modules . . . . . . . . . . . . . . . . . . . .37
Installing a microprocessor . . . . . . . . . . . . . . . . . . . .39
Replacing the battery . . . . . . . . . . . . . . . . . . . . . .42
Replacing a fan assembly . . . . . . . . . . . . . . . . . . . . .45
Completing the installation . . . . . . . . . . . . . . . . . . . . .47
Connecting the cables . . . . . . . . . . . . . . . . . . . . .48
Updating the server configuration . . . . . . . . . . . . . . . . .48
Chapter 5. I/O connectors . . . . . . . . . . . . . . . . . . . .51
Ethernet connector . . . . . . . . . . . . . . . . . . . . . . .51
Serial connector . . . . . . . . . . . . . . . . . . . . . . . .52
Universal Serial Bus connectors . . . . . . . . . . . . . . . . . .52
Video connector . . . . . . . . . . . . . . . . . . . . . . . .52
Chapter 6. Service replaceable units . . . . . . . . . . . . . . . .53
Removing a microprocessor . . . . . . . . . . . . . . . . . . . .54
Thermal grease . . . . . . . . . . . . . . . . . . . . . . . . .55
Power supply . . . . . . . . . . . . . . . . . . . . . . . . .56
Operator information card . . . . . . . . . . . . . . . . . . . . .58
CD-ROM drive . . . . . . . . . . . . . . . . . . . . . . . . .59
SCSI backplane . . . . . . . . . . . . . . . . . . . . . . . .60
Riser card . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Baseboard management controller . . . . . . . . . . . . . . . . . .62
System board . . . . . . . . . . . . . . . . . . . . . . . . .64
System board internal connectors . . . . . . . . . . . . . . . . .64
System-board external connectors . . . . . . . . . . . . . . . . .65
System-board LEDs . . . . . . . . . . . . . . . . . . . . . .66
System-board option connectors . . . . . . . . . . . . . . . . .67
System-board connectors for adapters, DIMMs, and other components . . .68
System-board switches and jumpers . . . . . . . . . . . . . . . .69
Removing the system board . . . . . . . . . . . . . . . . . . .70
Chapter 7. Symptom-to-FRU index . . . . . . . . . . . . . . . . .73
Beep symptoms . . . . . . . . . . . . . . . . . . . . . . . .74
No-beep symptoms . . . . . . . . . . . . . . . . . . . . . . .75
Diagnostic error codes . . . . . . . . . . . . . . . . . . . . . .76
Error symptoms . . . . . . . . . . . . . . . . . . . . . . . .78
POST error codes . . . . . . . . . . . . . . . . . . . . . . . .84
Service processor error codes . . . . . . . . . . . . . . . . . . .86
ServeRAID error codes . . . . . . . . . . . . . . . . . . . . . .86
POST (ISPR) error procedures . . . . . . . . . . . . . . . . . . .88
SCSI error codes . . . . . . . . . . . . . . . . . . . . . . . .90
Undetermined problems . . . . . . . . . . . . . . . . . . . . .91
Problem determination tips . . . . . . . . . . . . . . . . . . . .92
Chapter 8. Parts listing, Type 8835 . . . . . . . . . . . . . . . . .93
System . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Power cord CRUs . . . . . . . . . . . . . . . . . . . . . . . .96
Appendix A. Getting help and technical assistance . . . . . . . . . .99
Before you call . . . . . . . . . . . . . . . . . . . . . . . . .99
Using the documentation . . . . . . . . . . . . . . . . . . . . .99
Getting help and information from the World Wide Web . . . . . . . . . .99
vi Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Software service and support . . . . . . . . . . . . . . . . . . . 100
Hardware service and support . . . . . . . . . . . . . . . . . . . 100
Appendix B. Related service information . . . . . . . . . . . . . . 101
Safety information . . . . . . . . . . . . . . . . . . . . . . . 101
General safety . . . . . . . . . . . . . . . . . . . . . . . 101
Electrical safety . . . . . . . . . . . . . . . . . . . . . . . 102
Safety inspection guide . . . . . . . . . . . . . . . . . . . . 103
Handling electrostatic discharge-sensitive devices . . . . . . . . . . 104
Grounding requirements . . . . . . . . . . . . . . . . . . . . 104
Safety notices (multilingual translations) . . . . . . . . . . . . . . 104
Appendix C. Notices . . . . . . . . . . . . . . . . . . . . . . 143
Edition notice . . . . . . . . . . . . . . . . . . . . . . . . . 143
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Important notes . . . . . . . . . . . . . . . . . . . . . . . . 144
Product recycling and disposal . . . . . . . . . . . . . . . . . . 145
Battery return program . . . . . . . . . . . . . . . . . . . . . 145
Electronic emission notices . . . . . . . . . . . . . . . . . . . . 146
Federal Communications Commission (FCC) statement . . . . . . . . 146
Industry Canada Class A emission compliance statement . . . . . . . . 146
Australia and New Zealand Class A statement . . . . . . . . . . . . 146
United Kingdom telecommunications safety requirement . . . . . . . . 146
European Union EMC Directive conformance statement . . . . . . . . 146
Taiwanese Class A warning statement . . . . . . . . . . . . . . . 147
Chinese Class A warning statement . . . . . . . . . . . . . . . . 147
Japanese Voluntary Control Council for Interference (VCCI) statement 147
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Contents vii
viii Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 1. General information
The IBM Eserver 325 Type 8835 server is a 1-U-high
high-volume network transaction processing. This high-performance, symmetric
multiprocessing (SMP) server is ideally suited for networking environments that
require superior microprocessor performance, input/output (I/O) flexibility, and high
manageability.
Performance, ease of use, reliability, and expansion capabilities were key
considerations in the design of your server. These design features make it possible
for you to customize the system hardware to meet your needs today and provide
flexible expansion capabilities for the future.
The model number and serial number are on the ID label on the right mounting
bracket on the server, as shown in the following illustration.
Note: This illustration shows a SCSI model server. An IDE non-hot-swap hard disk
drive model is also available. This illustration might differ slightly from your
hardware.
1
rack model server for
ID label
If you have access to the Internet, you can obtain up-to-date information about your
server and other IBM server products at http://www.ibm.com/eserver/xseries/.
For service, assistance, or information, see Appendix A, “Getting help and technical
assistance,” on page 99.
1. Racks are marked in vertical increments of 1.75 inches each. Each increment is referred to as a unit, or a “U”. A 1-U-high device
is 1.75 inches tall.
© Copyright IBM Corp. 2002, 2003 1
Related publications
This Hardware Maintenance Manual and Troubleshooting Guide is provided in
Portable Document Format (PDF). It contains information to help you solve a
problem yourself or to provide helpful information to a service technician.
In addition to this Hardware Maintenance Manual and Troubleshooting Guide, the
following Eserver 325 documentation is provided with your server:
v Installation Guide
This printed publication contains instructions for setting up your server and basic
instructions for installing some options.
v User’s Guide
This publication provides general information about the server, including
information about features, how to configure the server, and how to get help.
v Option Installation Guide
This publication is in PDF on the IBM Eserver Documentation CD. It contains
detailed instructions for installing, removing, and connecting optional devices that
your server supports.
v Rack Installation Instructions
This printed publication contains instructions for installing your server in a rack
cabinet.
v Safety Information
This publication is in PDF on the IBM Eserver Documentation CD. It contains
translated caution and danger statements. Each caution and danger statement
that appears in the documentation has a number that you can use to locate the
corresponding statement in your language in the Safety Information book.
Depending on your server model, additional publications might be included on the
IBM Eserver Documentation CD.
Notices and statements used in this book
The caution and danger statements that appear in this book are also in the
multilingual Safety Information book, which is on the IBM Eserver Documentation
CD. Each statement is numbered for reference to the corresponding statement in
the Safety Information book.
The following notices and statements are used in the documentation:
v Notes: These notices provide important tips, guidance, or advice.
v Important: These notices provide information or advice that might help you avoid
inconvenient or problem situations.
v Attention: These notices indicate potential damage to programs, devices, or
data. An attention notice is placed just before the instruction or situation in which
damage could occur.
v Caution: These statements indicate situations that can be potentially hazardous
to you. A caution statement is placed just before the description of a potentially
hazardous procedure step or situation.
v Danger: These statements indicate situations that can be potentially lethal or
extremely hazardous to you. A danger statement is placed just before the
description of a potentially lethal or extremely hazardous procedure step or
situation.
2 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Features and specifications
The following table provides a summary of the features and specifications of your
Eserver 325 Type 8835 server. Depending on your server model, some features
might not be available, or some specifications might not apply.
Table 1. Features and specifications
Microprocessor:
™
v AMD Opteron
200 Series Processor
(one to two-way)
– Minimum: One
– Maximum: Two
1024 KB Level-2 cache
v
Use the Configuration/Setup Utility
Note:
program to determine the type and speed
of the microprocessors in your server.
Memory:
™
v AMD HyperTransport
technology
v Type: Error correcting code (ECC),
double-data rate (DDR) SDRAM,
registered DIMMs with Chipkill
™
memory protection
– Minimum: 1 GB
– Maximum: 6 GB (12 GB with
availability of 2 GB DIMMs)
– Installable in pairs
Four interleaved slots with standard
v
microprocessor
v Two interleaved slots with optional
microprocessor
Drives:
v CD-ROM: slim IDE (standard)
v Hard disk drives
– Slim-high 3.5-inch drives, hot-swap
SCSI or non-hot-swap IDE (drive
capacity and speed vary with
model)
– Maximum: Two
Expansion
slots:
v One full-length adapter slot supports
up to 100 MHz/64-bit PCI-X adapters
(bus 3)
v One half-length adapter slot supports
up to 100 MHz/64-bit PCI-X adapters
(bus 3)
v Supports 3.3 V or universal adapters
only
controller:
Video
v ATI RageXL video controller integrated
on system board
v Compatible with SVGA
v 8 MB SDRAM video memory
Power supply:
One 411 watt (115-230 V ac)
Size:
v Height 43 mm (1.69 in.)
v Depth: 660 mm (25.98 in.)
v Width: 440 mm (17.32 in.)
v Weight: approximately 12.7 kg (28 lb)
when fully configured
Integrated functions:
v Baseboard management controller
v One single-channel LSI Ultra320 SCSI
controller
v Two Broadcom 10/100/1000 Ethernet
controllers (dual-port design) with Wake
on LAN
v Four Universal Serial Bus (USB) ports
v One serial port
v One video port
Acoustical
v Declared sound power, idling: 6.5 bels
v Declared sound power, operating: 6.5
bels
Environment:
v Air temperature:
– Server on: 10° to 35°C (50.0° to
95.0°F). Altitude: 0 to 914 m (2998.7
ft)
– Server on: 10° to 32°C (50.0° to
89.6°F). Altitude: 914 m (2998.7 ft) to
2133 m (6998.0 ft.)
– Server off: 10° to 43°C (50.0° to
109.4°F). Maximum altitude: 2133 m
(6998.0 ft)
Humidity:
v
– Server on: 8% to 80%
– Server off: 8% to 80%
v Airflow rates:
– Minimum: 28 CFM
– Maximum: 47 CFM
®
noise emissions:
Heat output:
Approximate heat output in British thermal
units (Btu) per hour for dual multiprocessor
configurations:
v Minimum configuration: 789 Btu (230
watts)
v Maximum configuration: 1619 Btu (472
watts)
Electrical
input:
v Sine-wave input (50-60 Hz) required
v Input voltage low range:
– Minimum: 100 V ac
– Maximum: 127 V ac
Input voltage high range:
v
– Minimum: 200 V ac
– Maximum: 240 V ac
Input kilovolt-amperes (kVA),
v
approximately:
– Minimum: 0.12 kVA
– Maximum: 0.40 kVA
Notes:
1. Power consumption and heat output vary
depending on the number and type of
optional features installed and the
power-management optional features in
use.
2. These levels were measured in controlled
acoustical environments according to the
procedures specified by the American
National Standards Institute (ANSI)
S12.10 and ISO 7779 and are reported in
accordance with ISO 9296. Actual
sound-pressure levels in a given location
might exceed the average values stated
because of room reflections and other
nearby noise sources. The declared
sound-power levels indicate an upper
limit, below which a large number of
computers will operate.
Chapter 1. General information 3
Server controls, LEDs, and power
This section describes the controls and light-emitting diodes (LEDs) and how to turn
the server on and off.
Front view
The following illustration shows the controls, LEDs, and connectors on the front of
the server.
CD-ROM drive
activity LED
CD-ROM drive activity LED: When this LED is lit, it indicates that the CD-ROM
drive is in use.
CD-eject button
Hard disk drive
status LEDs
USB connectors
Hard disk drive
activity LEDs
Operator
information
panel
Power-on LED
Power-control
button
Reset button
CD-eject button: Press this button to release a CD from the CD-ROM drive.
Hard disk drive activity LEDs: When one of these LEDs is flashing, it indicates
that the associated SCSI hard disk drive is in use.
Power-on LED: When this LED is lit and not flashing, it indicates that the server is
turned on. When this LED is flashing, it indicates that the server is in turned off and
still connected to an ac power source. When this LED is off, it indicates that ac
power is not present, or the power supply or the LED itself has failed. A power-on
LED is also on the rear of the server.
Note: If this LED is off, it does not mean that there is no electrical power in the
server. The LED might be burned out. To remove all electrical power from
the server, you must disconnect the power cord from the electrical outlet.
Power-control button: Press this button to turn the server on and off manually.
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.
Operator information panel: This panel contains LEDs. The following illustration
shows the LEDs on the operator information panel.
Hard disk drive
activity LED
4 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Systemlocator
LED
Information
LED
Systemerror
LED
v Hard disk drive (HDD) activity LED: When this LED is lit, it indicates that either of
the hard disk drives is in use.
v System locator LED: Use this blue LED to visually locate the server if it is in a
location with numerous other servers. If your server supports IBM Director, you
can use IBM Director to light this LED remotely.
v Information LED: When this LED is lit, it indicates that a noncritical event has
occurred and is recorded in the error log. An LED near the failing component on
the system board is also lit to help isolate the error (see “Error LEDs” on page
20).
v System-error LED: When this LED is lit, it indicates that a system error has
occurred. A system-error LED is also on the rear of the server. An LED near the
failing component on the system board is also lit to help isolate the error (see
“Error LEDs” on page 20).
USB connectors: Connect USB devices to these connectors.
Notes:
1. If you want to attach a keyboard or mouse to this server, you must use a USB
keyboard or a USB mouse.
After installing a USB keyboard, you might need to use the Configuration/Setup
Utility program to enable keyboardless operation and prevent POST error
message 301 from being displayed during startup. For detailed information
about this option and how to connect it to your server, see the documentation
that comes with the option. For information about the Configuration/Setup Utility
program, see “Using the Configuration/Setup Utility program” on page 9.
2. Use an external USB diskette drive if:
v You want to attach a diskette drive to this server.
v You need to create an update diskette that contains the latest server firmware
code (see “Using the baseboard management controller firmware update
utility program” on page 11).
v You need to create update diskettes that contain the latest server BIOS code
(see “Updating BIOS code” on page 21).
Rear view
Hard disk drive status LEDs: When these LEDs are lit, it indicates that the
associated SCSI hard disk drive has failed. If an optional RAID adapter is installed
in the server and the LED flashes slowly (one flash per second), the drive is being
rebuilt. If the LED flashes rapidly (three flashes per second), the controller is
identifying the drive.
The following illustration shows the connectors and LEDs on the rear of the server.
Power-cord
connector
Serial
connector
Video
connector
Activity LEDs
USB connectors
Link LEDs
System-error LED
Power-on LED
Gigabit Ethernet 1
connector (LAN1)
Gigabit Ethernet 2
connector (LAN2)
Power-cord connector: Connect the power cord to this connector.
Chapter 1. General information 5
Activity LEDs (Ethernet): These green LEDs are on the dual Ethernet connector.
When either LED flashes, it indicates that data is being transmitted or received
between the server and the network device that is connected to the left or right
connector.
Link LEDs (Ethernet): These LEDs are on the dual Ethernet connector. When
either the up- or down-arrow LED is lit, it indicates that there is an active link
between the server and the network device that is connected to the left or right
connector. The flashing frequency is proportional to the amount of traffic on the
network link.
System-error LED: When this LED is lit, it indicates that a system error has
occurred. An LED near the failing component on the system board is also lit to help
isolate the error. A system-error LED is also on the front of the server.
Power-on LED: When this LED is lit and not flashing, it indicates that the server is
turned on. When this LED is flashing, it indicates that the server is in turned off and
still connected to an ac power source. When this LED is off, it indicates that ac
power is not present, or the power supply or the LED itself has failed. A power-on
LED is also on the front of the server.
Note: If this LED is off, it does not mean that there is no electrical power in the
server. The LED might be burned out. To remove all electrical power from
the server, you must disconnect the power cord from the electrical outlet.
Gigabit Ethernet 1 (LAN 1) connector: Use this connector to connect the server
to a network.
Gigabit Ethernet 2 (LAN 2) connector: Use this connector to connect the server
to a network.
USB connectors: Connect USB devices to these connectors.
Serial connector: Connect a 9-pin serial device to this connector.
If you have an optional Remote Supervisor Adapter II (system-management
adapter) installed in PCI slot 2, the server has additional connectors and LEDs. See
the documentation that comes with the adapter for more information about these
connectors and LEDs.
Server power features
When the server is connected to an ac power source but is not turned on, the
operating system does not run, and all core logic except for the service processor is
shut down; however, the server can respond to requests from the service processor,
such as a remote request to turn on the server. The power-on LED flashes to
indicate that the server is connected to ac power but not turned on.
Turning on the server
Approximately 20 seconds after the server is connected to ac power, the
power-control button becomes active and you can turn on the server and start the
operating system by pressing the power-control button.
The server can also be turned on in any of the following ways:
v If a power failure occurs while the server is turned on, the server will restart
automatically when power is restored.
6 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
v If the server is connected to an Advanced System Management interconnect
network that contains at least one server with an optional Remote Supervisor
Adapter II installed, the server can be turned on from the Remote Supervisor
Adapter II user interface.
v If your operating system supports the system-management software for an
optional Remote Supervisor Adapter II, the system-management software can
turn on the server.
v If your operating system supports the Wake on LAN feature, the Wake on LAN
feature can turn on the server.
Turning off the server
When you turn off the server and leave it connected to ac power, the server can
respond to requests from the service processor, such as a remote request to turn
on the server. To remove all power from the server, you must disconnect it from the
power source.
Some operating systems require an orderly shutdown before you turn off the server.
See your operating-system documentation for information about shutting down the
operating system.
Statement 5
CAUTION:
The power control button on the device and the power switch on the power supply do
not turn off the electrical current supplied to the device. The device also might have
more than one power cord. To remove all electrical current from the device, ensure
that all power cords are disconnected from the power source.
2
1
The server can be turned off in any of the following ways:
v You can turn off the server from the operating system, if your operating system
supports this feature. After an orderly shutdown of the operating system, the
server will be turned off automatically.
v You can press the power-control button to start an orderly shutdown of the
operating system and turn off the server, if your operating system supports this
feature.
v If the operating system stops functioning, you can press and hold the
power-control button for more than 4 seconds to turn off the server.
v If the server is connected to an Advanced System Management interconnect
network that contains at least one server with an optional Remote Supervisor
Adapter II installed, the server can be turned off from the Remote Supervisor
Adapter II user interface.
v If an optional Remote Supervisor Adapter II is installed in the server, the server
can be turned off from the Remote Supervisor Adapter II user interface.
v If the Wake on LAN feature turned on the server, the Wake on LAN feature can
turn off the server.
Chapter 1. General information 7
v The integrated system management processor can turn off the server as an
automatic response to a critical system failure.
v You can turn off the server through a request from the service processor.
8 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 2. Configuration
Note: Detailed information about configuration is available in the User’s Guide for
this server.
The following configuration programs and capabilities come with your server:
v Configuration/Setup Utility program
The Configuration/Setup Utility program is part of the basic input/output system
(BIOS) code in your server. Use it to configure serial port assignments, change
interrupt request (IRQ) settings, change the startup-device sequence, set the
date and time, and set passwords.
v Ethernet controller configuration
Detailed information about configuring the Ethernet controllers can be found in
the User’s Guide for this server.
v Baseboard management controller firmware update utility program
For information about updating the baseboard management controller firmware,
see “Using the baseboard management controller firmware update utility
program” on page 11.
v RAID configuration programs
– LSI Logic Configuration Utility program
Use the LSI Logic Configuration Utility to configure the integrated SCSI
controller with RAID capabilities and the devices that are attached to it.
– ServeRAID Manager
ServeRAID
Director extension. If a ServeRAID adapter is installed in your server or if you
are using the RAID capabilities of the SCSI controller, use ServeRAID
Manager to define and configure your disk-array subsystem before you install
the operating system. For more information on these programs, see the
User’s Guide for this server.
™
Manager is available as a stand-alone program and as an IBM
intends to make IBM Director and the Remote Supervisor Adapter II available
IBM
in the future. To determine the availability of these features, go to
http://www.ibm.com/pc/support/.
Using the Configuration/Setup Utility program
The Configuration/Setup Utility program is part of the BIOS code. You can use it to:
v View configuration information
v View and change assignments for devices and I/O ports
v Set the date and time
v Set and change passwords
v Set and change the startup characteristics of the server and the order of startup
devices (startup-drive sequence)
v Set and change settings for advanced hardware features
v View, set, and change settings for power-management features
v View and clear error logs
v Change interrupt request (IRQ) settings
v Enable USB keyboard and mouse support (default)
© Copyright IBM Corp. 2002, 2003 9
Starting the Configuration/Setup Utility program
Complete the following steps to start the Configuration/Setup Utility program:
1. Turn on the server.
2. When the prompt Press F1 for Configuration/Setup appears, press F1. If you
have set both a user (power-on) password and a supervisor (administrator)
password, you must type the supervisor password to access the full
Configuration/Setup Utility menu. If you do not type the supervisor password, a
limited Configuration/Setup Utility menu is available.
3. Follow the instructions on the window.
4. Select settings to view or change.
more information on using the Configuration/Setup Utility program, see the IBM
For
Eserver 325 User’s Guide on the IBM Eserver Documentation CD.
Using the RAID configuration programs
Use the LSI Logic Configuration Utility program and ServeRAID Manager to
configure and manage redundant array of independent disks (RAID) arrays. Be sure
to use these programs as described in this book.
v Use the LSI Logic Configuration Utility program to:
– Perform a low-level format on a SCSI hard disk drive
– View or change SCSI IDs for attached devices
– Set SCSI protocol parameters on SCSI hard disk drives
v Use ServeRAID Manager to:
– Configure arrays
– View your RAID configuration and associated devices
– Monitor operation of your RAID controllers
Detailed
information about these programs is available in the User’s Guide that
comes with this server.
Configuring the Gigabit Ethernet controllers
Two Ethernet controllers are integrated on the system board. For information about
configuring your Ethernet controllers, see the Broadcom NetXtreme Gigabit Ethernet
Software CD that comes with your server. For updated information about
configuring your Ethernet controllers, go to the IBM Support Web site at
http://www.ibm.com/pc/support/ and navigate to the area for your server machine
type. From this area, you can download documentation, the most current device
drivers for your server, and software that supports advanced networking functions.
After downloading, run the downloaded program launch.exe.
Note: To use the Wake on LAN features that appear on the configuration menu,
your server must contain Wake on LAN hardware and software and your
operating system must support Wake on LAN functions.
10 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Using the baseboard management controller firmware update utility
program
To update the firmware for the baseboard management controller, download the
baseboard management controller Firmware Update Diskette for your server from
the IBM Support Web site at http://www.ibm.com/pc/support/. Run the program to
create a diskette or to create the Linux or Windows
use to update the firmware. The firmware update program updates the baseboard
management controller firmware only and does not affect any device drivers.
Note: To ensure proper server operation, be sure to update the server baseboard
management controller firmware code first before updating the BIOS code.
For additional information, see the User’s Guide on the IBM Eserver
Documentation CD.
Complete the following steps to update the firmware:
v Using Linux or Windows, run the Linux or Windows update package obtained
from the web (if available).
v Using a diskette:
1. Turn off the server.
2. Insert the Firmware Update Diskette into an external USB diskette drive that
you have attached to the server.
3. Turn on the server. If the server does not start from the external USB diskette
drive, use the Configuration/Setup Utility program to configure the external
USB diskette drive as a startup device. (For more information, see the
information about Configuration/Setup Utility startup sequences in the User’s
Guide on the IBM Eserver Documentation CD). Then, start again at step 1
of this procedure.
4. From a command-line prompt, type update.bat and press Enter.
®
update package that you can
there is an error in updating the firmware, try installing the firmware again.
If
Chapter 2. Configuration 11
12 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 3. Diagnostics
This chapter provides basic troubleshooting information to help you solve some
common problems that might occur with the server.
If you cannot locate and correct the problem using the information in this chapter,
see Appendix A, “Getting help and technical assistance,” on page 99 for more
information.
General checkout
The diagnostic programs are on the IBM Enhanced Diagnostics CD. These
programs are the primary method of testing the major components of the server:
the system board, Ethernet controller, video controller, RAM, keyboard, mouse
(pointing device), serial ports, hard disk drives, and parallel port. You can also use
them to test some external devices. See “Diagnostic programs and error messages”
on page 16..
Also, if you cannot determine whether a problem is caused by the hardware or by
the software, you can run the diagnostic programs to confirm that the hardware is
working correctly.
When you run the diagnostic programs, a single problem might cause several error
messages. When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages
might not occur the next time you run the test.
A failed server might be part of a shared hard disk drive cluster (two or more
servers sharing the same external storage devices). Before running the diagnostic
programs, make sure that the failing server is not part of a shared hard disk drive
cluster.
A server might be part of a cluster if one or more of the following is true:
v The customer identifies the server as part of a cluster.
v One or more external storage units are attached to the server and at least one of
the attached storage units is additionally attached to another server or
unidentifiable source.
v One or more servers are located near the failing server.
If the failing server is suspected to be part of a shared hard disk drive cluster, all
diagnostic tests can be run except diagnostic tests that test the storage unit (a hard
disk drive in the storage unit) or the storage adapter that is attached to the storage
unit.
Notes:
1. For servers that are part of a shared hard disk drive cluster, run one test at a
time in looped mode. Do not run all tests in looped mode, because this could
enable the hard disk drive diagnostic tests.
2. If multiple error codes are displayed, diagnose the first error code that is
displayed.
3. If the server is suspended with a POST error, go to “POST error codes” on
page 84.
© Copyright IBM Corp. 2002, 2003 13
4. If the server is suspended and no error message is displayed, see “Error
symptoms” on page 78 and “Undetermined problems” on page 91.
5. For information about power-supply problems, see “Power checkout” on page
24 and Chapter 7, “Symptom-to-FRU index,” on page 73
6. For safety information, see “Safety information” on page 101.
7. For intermittent problems, check the error log; see “POST error messages” on
page 16 and “Diagnostic programs and error messages” on page 16.
Checkout procedure
Complete the following steps to perform the checkout procedure.
001 IS THE SERVER PART OF A CLUSTER?
002 IF THE SERVER IS NOT PART OF A CLUSTER:
YES. Schedule maintenance with the customer. Shut down all
servers related to the cluster. Run the storage test.
NO. Go to step 002.
1. Turn off the server and all external devices.
2. Check all cables and power cords.
3. Set all display controls to the middle position.
4. Turn on all external devices.
5. Turn on the server.
6. Record any POST error messages that are displayed on the
screen. If an error is displayed, look up the first error in the
“POST error codes” on page 84.
7. Check the System Error log. If an error was recorded by the
server, see Chapter 7, “Symptom-to-FRU index,” on page 73.
8. Start the diagnostic programs. See “Diagnostic programs and
error messages” on page 16.
9. Check for the following responses:
a. One beep
b. Readable instructions or the main menu
DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
003
NO. Find the failure symptom in Chapter 7, “Symptom-to-FRU
index,” on page 73.
YES. Run the diagnostic programs. If necessary, see “Diagnostic
programs and error messages” on page 16.
If you receive an error, see Chapter 7, “Symptom-to-FRU index,” on
page 73.
If the diagnostics were completed successfully and you still suspect
a problem, see “Undetermined problems” on page 91.
14 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Diagnostic tools overview
The following tools are available to help you diagnose and solve hardware-related
problems:
v POST beep codes and error messages
The power-on self-test (POST) generates beep codes and messages to indicate
successful test completion or the detection of a problem. See “Power-on self-test”
for more information.
v Diagnostic programs
The diagnostic programs are stored on the IBM Enhanced Diagnostics CD.
These programs are the primary method of testing the major components of the
server. See “Diagnostic programs and error messages” on page 16 for more
information.
v Error charts
These charts list problem symptoms and steps to correct the problem. See “Error
charts” on page 19 for more information.
v Symptom-to-FRU index
This index lists problem symptoms and steps to correct each problem. See
Chapter 7, “Symptom-to-FRU index,” on page 73 for more information.
Power-on self-test
When you turn on the server, the power on self-test (POST) performs a series of
tests to check the operation of system components and some of the installed
options.
If POST finishes without detecting any problems, the first window of the operating
system opens or an application program appears.
If POST detects a problem, more than one beep might sound, and an error
message appears on the screen.
Notes:
1. If you have a user password set, you must type the password and press Enter,
2. A single problem might cause several error messages. When this occurs, work
POST beep codes
POST generates beep codes to indicate successful completion or the detection of a
problem.
v One short beep indicates the successful completion of POST.
v More than one beep indicates that POST detected a problem. For more
information, see “Beep symptoms” on page 74.
when prompted, before the operating system will start.
to correct the cause of the first error message. After you correct the cause of
the first error message, the other error messages usually will be resolved the
next time you run the test.
If POST detects a problem (more than one beep sounds), an error message
appears on the screen. See “Beep symptoms” on page 74 and “POST error codes”
on page 84 for more information.
Chapter 3. Diagnostics 15
POST error messages
POST error messages can appear when a problem is detected during startup. For a
complete list of POST messages, see “POST error codes” on page 84.
Diagnostic programs and error messages
The system diagnostic programs are stored on the IBM Enhanced Diagnostics CD.
These programs are the primary method of testing the major components of the
server.
The IBM Enhanced Diagnostics programs isolate problems from the server
hardware and software. The programs run independently of the operating system
and must be run either from a CD or diskette. If you want to run the diagnostic
programs from a diskette, you must attach an external USB diskette drive to the
server.
Diagnostic error messages indicate that a problem exists; they are not intended to
be used to identify a failing part. Troubleshooting and servicing complex problems
indicated by error messages should be performed by trained service personnel.
Sometimes the first error to occur causes additional errors. In this case, the server
displays more than one error message. Always follow the suggested action
instructions for the first error message that appears.
Error codes that might be displayed are listed at “Diagnostic error codes” on page
76.
The error code format is as follows:
fff-ttt-iii-date-cc-text message
where:
fff is the three-digit function code that indicates the function being tested when
the error occurred. For example, function code 201 is for memory.
ttt is the three-digit failure code for the exact test failure. (These codes are for
trained service personnel.)
iii is the three-digit device ID. (These codes are for trained service personnel.)
date is the date that the diagnostic test was run and the error recorded.
cc are the check digits that are used to verify the validity of the information.
text message
is the diagnostic message that indicates the reason for the problem.
16 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Text messages
The diagnostic text message format is as follows:
Function Name: Result (test specific string)
where:
Function Name
is the name of the function being tested when the error occurred. This
corresponds to the function code (fff) described in the previous list.
Result
can be one of the following text strings:
Passed
This result occurs when the diagnostic test is completed without
any errors.
Failed This result occurs when the diagnostic test discovers an error.
User Aborted
This result occurs when you stop the diagnostic test before it is
complete.
Not Applicable
This result occurs when you specify a diagnostic test for a device
that is not present.
Aborted
This result occurs when the test could not proceed because of the
system configuration.
Warning
This result occurs when a possible problem is reported during the
diagnostic test, such as when a device that is to be tested is not
installed.
specific string
test
is additional information that is used to analyze the problem.
Downloading the diagnostics program
Complete the following steps to download the latest image of the IBM Enhanced
Diagnostics and create a startable Enhanced Diagnostics diskette:
1. Go to http://www.ibm.com/pc/support/.
2. Download the diagnostics file for the server to a hard disk drive directory (not to
a diskette).
3. Go to a DOS prompt, and change to the directory where the file was
downloaded.
4. Insert a blank high-density diskette into the diskette drive.
Note: On the Eserver 325 server, attach an external USB diskette drive to the
server for this purpose.
5. Type in the following, and then press Enter: filename a: where filename is the
name of the file you downloaded from the Web.
downloaded file is self-extracting and is copied to the diskette. When the copy
The
is completed, you have a startable or bootable IBM Enhanced Diagnostics diskette.
Chapter 3. Diagnostics 17
Starting the diagnostic programs and viewing the test log
The IBM Enhanced Diagnostics programs isolate problems from the server
hardware and software. The programs run independently of the operating system
and must be run either from a CD or diskette. This method of testing is generally
used when other methods are not accessible or have not been successful in
isolating a problem suspected to be hardware related.
An IBM Enhanced Diagnostics CD comes with the server. Yo u can also download
the latest version of the diagnostic programs from http://www.ibm.com/pc/support/.
The test log records data about system failures and other pertinent information. The
following sections describe the diagnostic procedure for the diagnostics CD and the
diagnostics diskette.
Using the diagnostics CD
To start the IBM Enhanced Diagnostics using the CD, complete the following steps:
1. Turn off the server and any peripheral devices.
2. Turn on all attached devices; then, turn the server on.
3. When you see Press F1 For Configuration/Setup, press the F1 key.
4. When the Configuration/Setup Utility menu appears, select Start Options.
5. From the Start Options menu, select Startup Sequence.
6. Note the device selected as the First Startup Device. Later, you must restore
this setting.
7. Select CD-ROM as the First Startup Device.
8. Press Esc two times to return to the Configuration/Setup Utility menu.
9. Place the IBM Enhanced Diagnostics CD in the CD-ROM drive.
10. Select Save & Exit Setup and follow the prompts. The diagnostics will load.
Follow the instructions on the screen to run the diagnostics.
11. When the tests have completed, you can view the Test Log by selecting Utility
from the top of the screen. You can save the test log to a file on a diskette or
to your hard disk drive.
Important: When you finish running the diagnostics and utilities, remove the
CD from the CD-ROM drive and turn off the server. Yo u must
restore the First Startup Device to the original setting. Use steps 2
through 8 of this procedure to do this.
Note: The system maintains the test-log data while the system is powered on.
When you turn off the power to the server, the test log is cleared.
Using the diagnostic diskette
Do the following to start the IBM Enhanced Diagnostics using the diagnostics
diskette, do the following:
1. Turn off the server and any peripheral devices.
2. Insert the IBM Enhanced Diagnostics diskette into the external USB diskette
drive.
3. Turn on all attached devices; then, turn on the server.
4. Follow the instructions on the screen.
5. When the tests have completed, you can view the Test Log by selecting Utility
from the top of the screen. You can save the test log to a file on a diskette or to
your hard disk drive.
18 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Note: The system maintains the test-log data while the system is powered on.
When you turn off the power to the server, the test log is cleared.
6. When you have completed the diagnostics procedure, remove the diagnostic
diskette from the diskette drive before restarting the server.
If the hardware checks out OK but the problem persists during normal server
operations, a software error might be the cause. If you suspect a software problem,
refer to the information that comes with the software package.
Diagnostic error message tables
For descriptions of the error messages that might appear when you run the
diagnostic programs, see “Diagnostic error codes” on page 76.
Notes:
1. Depending on the configuration, some of the error messages might not appear
when you run the diagnostic programs.
2. If diagnostic error messages appear that are not listed in the tables, make sure
that the server has the latest level of BIOS code installed.
Error charts
You can use the error charts to find solutions to problems that have definite
symptoms (see “Error symptoms” on page 78).
Important: If diagnostic error messages are displayed that are not listed, make
sure that the system has the latest levels of BIOS code installed.
Small computer system interface (SCSI) messages (some models)
If the server has an Ultra320 SCSI adapter and you receive a SCSI error message,
see “SCSI error codes” on page 90.
Note: If the server does not have a SCSI hard disk drive, ignore any message that
indicates that the BIOS code is not installed.
Chapter 3. Diagnostics 19
Error LEDs
The system-error LED on the front panel (see “Front view” on page 4) is lit to
indicate that a system error has occurred. The system board has error LEDs for
microprocessors, fans and memory that will help to locate the source of the error.
Run the diagnostic programs (see “Starting the diagnostic programs and viewing
the test log” on page 18) to find out the cause of the error.
Microprocessor 1 error
LED (DLED13)
DIMM 4 error LED (DLED7)
DIMM 3 error LED (DLED5)
DIMM 2 error LED (DLED3)
DIMM 1 error LED (DLED1)
DIMM 6 error LED (DLED12)
Error/Power LED (J20)
DIMM 5 error LED (DLED9)
Fan 5 error LED (DLED10)
Fan 4 error LED (DLED8)
Fan 3 error
LED (DLED6)
SCSI LED
header (J19)
Fan 1 error
LED (DLED2)
Fan 2 error
LED (DLED4)
Microprocessor 2 error
LED (DLED14)
20 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Loading...