IBM xSeries 200 Hardware Maintenance Manual

Hardware Maintenance Manual

xSeries 200



:

Note: Before using this information and the product it

supports, be sure to read the general information
under “Notices” on page 167.

Fifth Edition (April 2008)

INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. Some states
do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not
apply to you.

This publication could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in
new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.

This publication was developed for products and services
offered in the United States of America. IBM may not offer
the products, services, or features discussed in this
document in other countries, and the information is subject
to change without notice. Consult your local IBM

representative for information on the products, services,
and features available in your area.

Requests for technical information about IBM products
should be made to your IBM reseller or IBM marketing
representative.

xSeries 200

© Copyright International Business Machines
Corporation 2000. All rights reserved.

US Government Users Restricted Rights – Use, duplication
or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

iii

iv Hardware Maintenance Manual: xSeries 200

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
xSeries 200.

Important: This manual is intended for trained servicers

who are familiar with IBM PC Server products.

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.

© Copyright IBM Corp. 2000 v

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.

Online support

Use the World Wide Web (WWW) to download Diagnostic,
BIOS Flash, and Device Driver files.

File download address is:

http://www.us.pc.ibm.com/files.html

IBM online addresses

The HMM manuals online address is:

http://www.us.pc.ibm.com/cdt/hmm.html

The IBM PC Company Support Page is:

http://www.us.pc.ibm.com/support/index.html

The IBM PC Company Home Page is:

http://www.pc.ibm.com

vi Hardware Maintenance Manual: xSeries 200

Contents

About this manual . . . . . . . . . . .v

Important safety information . . . . . . . . .v

Online support . . . . . . . . . . . . .vi

IBM online addresses . . . . . . . . . .vi

Chapter 1. General checkout . . . . . . . .1

Chapter 2. General information . . . . . . .3

Features and specifications . . . . . . . . .3

Server features . . . . . . . . . . . . .5

Reliability, availability, and serviceability . . . . . .6

Server controls and indicators . . . . . . . .7

Turning on the server . . . . . . . . . .8

Turning off the server . . . . . . . . . .8

Chapter 3. Diagnostics . . . . . . . . . .11

Diagnostic tools overview . . . . . . . . .11

POST . . . . . . . . . . . . . . .11

POST beep code descriptions . . . . . . .12

POST error messages . . . . . . . . .12

Small computer system interface messages (some

models) . . . . . . . . . . . . . .12

Diagnostic programs and error messages . . . . .13

Text messages . . . . . . . . . . .14

Starting the diagnostic programs . . . . . .15

Using the diagnostics CD . . . . . . .15

Downloading the diagnostics program . . . .16

Using the diagnostic diskette . . . . . .16

Viewing the test log . . . . . . . . . .17

Diagnostic error message tables . . . . . .17

Power checkout . . . . . . . . . . . .17

Recovering BIOS . . . . . . . . . . . .18

Clearing CMOS . . . . . . . . . . . .20

Replacing the battery . . . . . . . . . . .20

Temperature checkout . . . . . . . . . .22

Diagnosing errors . . . . . . . . . . . .23

Troubleshooting the Ethernet controller . . . . .23

Network connection problems . . . . . . .23

Ethernet controller troubleshooting chart . . . .24

Ethernet controller messages . . . . . . . .26

Novell NetWare or IntraNetWare system ODI driver

teaming messages . . . . . . . . .26

NDIS 4.0 (Windows NT) driver messages . . . .28

Ethernet teaming messages: . . . . . . .31

Chapter 4. Configuring the server . . . . . .33

Using the Configuration/Setup Utility program . . .33

Starting the Configuration/Setup Utility program 34
Choices available from the Configuration/Setup

main menu . . . . . . . . . . . .34

© Copyright IBM Corp. 2000 vii

Using passwords . . . . . . . . . . .36

Using the SCSISelect utility program (some models) 37

Starting the SCSISelect utility program . . . .38

Choices available from the SCSISelect menu . .38

Chapter 5. Installing options . . . . . . . .41

Expanded view of the xSeries 200 . . . . . . .41

System and PCI extender board . . . . . .41

System and PCI extender board options

connectors . . . . . . . . . . .41

System board internal cable connectors . . .42

System board external connectors . . . . .42

System board switches and jumpers . . . .43

Before you begin . . . . . . . . . . . .44

Working inside the server with the power on . . .44

System reliability considerations . . . . . .45

Handling static-sensitive devices . . . . . .45

Moving the stabilizing feet . . . . . . . . .46

Removing the side cover . . . . . . . . . .46

Removing the bezel . . . . . . . . . . .48

Removing the support bracket assembly . . . . .49

Working with adapters . . . . . . . . . .50

Adapter considerations . . . . . . . . .50

Installing an adapter . . . . . . . . . .51

Installing a SCSI or ServeRAID adapter (some models) 53

Installing internal drives . . . . . . . . . .54

Internal drive bays . . . . . . . . . .54

Preinstallation steps (all bays) . . . . . . .56

Installing a drive in bay 2 or 4 . . . . . . .56

Installing a hard disk drive in bay 5, 6, or 7 . . .59

Installing memory modules . . . . . . . . .61

Removing and installing a microprocessor . . . .63

Removing a microprocessor . . . . . . . .65

Installing a microprocessor . . . . . . . .66

Installing a security U-bolt . . . . . . . . .69

Completing the installation . . . . . . . . .70

Installing the cover . . . . . . . . . .70

Updating the server configuration . . . . . .72

Connecting external options . . . . . . . .72

Installation procedure . . . . . . . . .72

I/O connector locations . . . . . . . . .72

Input/output ports . . . . . . . . . . .73

Mouse port . . . . . . . . . . . .74

Keyboard port . . . . . . . . . . .74

Parallel connector . . . . . . . . . .75

Viewing or changing the connector

assignments . . . . . . . . .75

Parallel connector . . . . . . . . .75

Serial connectors . . . . . . . . . .76

Viewing or changing the serial-connector

assignments . . . . . . . . .76

Serial connectors . . . . . . . . .77

Ethernet connector . . . . . . . . .77

viii Hardware Maintenance Manual: xSeries 200

Configuring the Ethernet controller . . . .77

Failover for redundant Ethernet . . . . .78

High Performance Ethernet Modes . . . .78

Ethernet connector . . . . . . . .81

Universal Serial Bus connectors . . . . .82

USB cables and hubs . . . . . . .82

USB connectors . . . . . . . . .82

Audio connectors . . . . . . . . . .83

Line out . . . . . . . . . . . .83

Line in . . . . . . . . . . . .83

Mic . . . . . . . . . . . . .83

MIDI connector . . . . . . . . . .83

Video connector . . . . . . . . . .84

Ultra 3/160 SCSI connector (some models) 84

SCSI cabling requirements . . . . . .85

Setting SCSI IDs . . . . . . . . .85

Chapter 6. FRU information (service only) . . . .87

Hard disk drive cage . . . . . . . . . . .87

Power supply . . . . . . . . . . . . .88

Rear fan . . . . . . . . . . . . . .88

System board . . . . . . . . . . . . .89

CD-ROM drive . . . . . . . . . . . . .90

Floppy disk drive . . . . . . . . . . . .91

Button kit . . . . . . . . . . . . . .92

Guide assembly / speaker . . . . . . . . .93

Bezel release latch . . . . . . . . . . .94

Top/side cover . . . . . . . . . . . . .95

Handle assembly . . . . . . . . . . . .96

Adapter retainer . . . . . . . . . . . .96

Chapter 7. Symptom-to-FRU index . . . . . .99

Beep symptoms . . . . . . . . . . . .99

No beep symptoms . . . . . . . . . . . 103

Diagnostic error codes . . . . . . . . . . 103

Error symptoms . . . . . . . . . . . . 107

POST error codes . . . . . . . . . . .110

Processor board LEDs . . . . . . . . . .116

ServeRAID . . . . . . . . . . . . .116

Undetermined problems . . . . . . . . .116

Chapter 8. Parts listing . . . . . . . . .119

System . . . . . . . . . . . . . .119

Keyboards . . . . . . . . . . . . . 121

Power cords . . . . . . . . . . . . . 122

Chapter 9. Related service information . . . . 125

Safety information . . . . . . . . . . . 125

General safety . . . . . . . . . . . 125

Electrical safety . . . . . . . . . . . 126

Safety inspection guide . . . . . . . . . 128

Handling electrostatic discharge-sensitive devices 129

Grounding requirements . . . . . . . . 130

Contents ix

Safety notices (multi-lingual translations) . . . . 130

Send us your comments! . . . . . . . . . 166

Problem determination tips . . . . . . . . . 166

Notices . . . . . . . . . . . . . . 167

Trademarks . . . . . . . . . . . . . 168

x Hardware Maintenance Manual: xSeries 200

Chapter 1. General checkout

The server diagnostic programs are stored in upgradable
read-only memory (ROM) on the system board. 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), diskette drive, serial ports, hard drives,
and parallel port. Yo u can also use them to test some
external devices. See “Diagnostic programs and error
messages” on page 13.

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 properly.

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 system might be part of a shared DASD cluster
(two or more systems sharing the same external storage
device(s)). Prior to running diagnostics, verify that the
failing system is not part of a shared DASD cluster.

A system might be part of a cluster if:

v The customer identifies the system as part of a cluster.
v One or more external storage units are attached to the

system and at least one of the attached storage units is
additionally attached to another system or unidentifiable
source.

v One or more systems are located near the failing

system.

If the failing system is suspected to be part of a shared
DASD cluster, all diagnostic tests can be run except
diagnostic tests which test the storage unit (DASD residing
in the storage unit) or the storage adapter attached to the
storage unit.

Notes:

1. For systems that are part of a shared DASD cluster,
run one test at a time in looped mode. Do not run all
tests in looped mode, as this could enable the DASD
diagnostic tests.

2. If multiple error codes are displayed, diagnose the first
error code displayed.

© Copyright IBM Corp. 2000 1

3. If the computer hangs with a POST error, go to the
Chapter 7, “Symptom-to-FRU index,” on page 99.

4. If the computer hangs and no error is displayed, go to
“Undetermined problems” on page 116.

5. Power supply problems, see Chapter 7,
“Symptom-to-FRU index,” on page 99.

6. Safety information, see “Safety information” on page

125.

7. For intermittent problems, check the error log; see
“POST error messages” on page 12.

1. IS THE SYSTEM PART OF A CLUSTER?

YES. Schedule maintenance with the customer. Shut down

all systems related to the cluster. Run storage test.

NO. Go to step 2.

2.

IF THE SYSTEM IS NOT PART OF A CLUSTER:

v Power-off the computer and all external devices.
v Check all cables and power cords.
v Set all display controls to the middle position.
v Power-on all external devices.
v Power-on the computer.
v Record any POST error messages displayed on the

screen. If an error is displayed, look up the first error
in the “POST error codes” on page 110.

v Check the System Error Log. If an error was

recorded by the system, see Chapter 7,
“Symptom-to-FRU index,” on page 99.

v Start the Diagnostic Programs. See “Diagnostic

programs and error messages” on page 13.

v Check for the following responses:

a. One beep.
b. Readable instructions or the Main Menu.

3. DID YOU RECEIVE BOTH OF THE CORRECT

RESPONSES?

NO. Find the failure symptom in Chapter 7,

“Symptom-to-FRU index,” on page 99.

YES. Run the Diagnostic Programs. If necessary, refer to

“Diagnostic programs and error messages” on page 13.

If you receive an error, go to Chapter 7, “Symptom-to-FRU
index,” on page 99.

If the diagnostics completed successfully and you still
suspect a problem, see “Undetermined problems” on page

116.

2 Hardware Maintenance Manual: xSeries 200

Chapter 2. General information

The IBM® 200 server delivers great value for general
server applications. It is ideally suited for networking
environments that require superior microprocessor
performance, efficient memory management, flexibility, and
large amounts of reliable data storage.

The server serial number and model number are located
on labels on the rear and front of the server. With access
to the World Wide Web, up-to-date information about the
server model and other IBM server products is available at
the following World Wide Web address:
http://www.ibm.com/pc/us/eserver/xseries

Features and specifications

The following provides a summary of the features and
specifications for the 200 server. Depending on the server
model, some features and specifications might not apply.

© Copyright IBM Corp. 2000 3

Table 1. Features and Specifications

Microprocessor:

Supports one
microprocessor
(depending on your
model)

v Intel® Pentium® III

with 256 KB
Level-2 cache and
MMX™ (MMX2)
technology

or

v Intel® Celeron

®

with 128 KB
Level-2 cache and
MMX™ (MMX2)
technology

Memory:

v Minimum: 64 MB
v Maximum: 1.5 GB
v Type: PC133

MHz, ECC
SDRAM,
unregistered
DIMMs only

v Slots: 3 dual inline

Drives:

(depending

on your model)

v Diskette: 1.44 MB
v CD-ROM: IDE
v Hard disk drive

v

Tape drive

Expansion

bays:

v Two 5.25-in. bays

(one CD-ROM
drive installed)

v Two 3.5-in. bays

(one diskette drive
installed)

v Three 3.5-in.

slim-high bays
available

PCI

expansion

slots:

v Three 33

MHz/32-bit on the
system board
(some models
come with a SCSI
adapter installed)

v Two 33

MHz/32-bit on the
PCI Bus extender
board

AGP

slot:

Accelerated graphics
port (AGP)

Power supply:

One 330 watt
(90-240 V ac)

Video:

v S3 Savage 4

AGP video
adapter

v Compatible with

SVGA and VGA

v 8 MB SDRAM

video memory

Size:

v Height: 470 mm

(18.5 in.)

v Depth: 508 mm

(19.9 in.)

v Width: 165 mm

(6.5 in.)

v Weight:

approximately

19.5 Kg (43 lb.)
when fully
configured or

15.9 Kg (35 lb.)
minimum

Integrated
functions:

v

10BASE-T/
100BASE-TX
Ethernet controller
on the system
board

v Two serial ports
v One parallel port
v Two USB ports
v Keyboard port
v Mouse port
v MIDI port
v Audio ports

– Line out
– Line in
– Mic

v

Dual-channel bus

mastering IDE
controller

Acoustical

noise

emissions:

v Sound power,

idling: 6.6 bel
maximum

v Sound power,

operating: 6.8 bel
maximum

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.)

v Humidity:

– Server on: 8%

to 80%

– Server off: 8%

to 80%

Heat

output:

Approximate heat
output in British
Thermal Units (Btu)
per hour

v Minimum

configuration: 341
Btu (100 watts)

v Maximum

configuration: 1604
Btu (470 watts)

Electrical

input:

v Sine-wave input

(50-60 Hz)
required

v Input voltage low

range:
– Minimum: 90 V

ac

– Maximum: 137

V ac

v Input voltage high

range:
– Minimum: 180

V ac

– Maximum: 265

V ac

v Input

kilovolt-amperes
(kVA)
approximately:
– Minimum: 0.08

kVA

4 Hardware Maintenance Manual: xSeries 200

Server features

The design of the 200 takes advantage of advancements
in data storage and memory management. The server
combines:

v Impressive performance using an innovative approach to

microprocessor utilization
The server comes with one Celeron® or Pentium® III

microprocessor installed.

v Large system memory

The memory bus in the server supports up to 1.5
gigabytes (GB) of system memory. The memory
controller provides error code correction (ECC) support
for up to three industry-standard PC133, 3.3 V, 168-pin,
133 megahertz (MHz), unregistered, synchronous
dynamic random access memory (SDRAM) dual in-line
memory modules (DIMMs).

v Systems-management capabilities

See the documentation provided with the
systems-management software for more information.

v Integrated network environment support

The server comes with an Ethernet controller on the
system board. This Ethernet controller has an interface
for connecting to 10-Mbps or 100-Mbps networks. The
server automatically selects between 10BASE-T and
100BASE-TX environments. The controller provides
full-duplex (FDX) capability, which allows simultaneous
transmission and reception of data on the Ethernet local
area network (LAN).

v IBM ServerGuide™ CDs

The ServerGuide CDs included with IBM servers provide
programs to help set up the server and install the
network operating system (NOS). The ServerGuide
program detects the hardware options installed, and
provides the correct configuration program and device
drivers. In addition, the ServerGuide CDs include a
variety of application programs for the server.

Note: The latest level of BIOS for the server is also

available through the World Wide Web. Refer to
“Recovering BIOS” on page 18 for the
appropriate World Wide Web addresses.

Chapter 2. General information 5

Reliability, availability, and serviceability

Three of the most important considerations in server
design 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 needed, and the ease with which you can diagnose
and repair problems.

The following is an abbreviated list of the RAS features
that the server supports. Many of these features are
explained in the following chapters of this book.

v Reliability features

– Boot block recovery
– Cooling fans with speed-sensing capability
– Customer-upgradable basic input/output system

(BIOS)
– ECC front-side buses (FSBs)
– ECC L2 cache
– ECC memory
– Parity checking on the small computer system

interface (SCSI) and peripheral component

interconnect (PCI) buses
– Advanced configuration and power interface (ACPI)
– Power-on self-test (POST)
– Synchronous dynamic random access memory

(SDRAM) with serial presence detect (SPD)

v

Availability features

– Advanced desktop management interface (DMI)

features
– Alarm on LAN™ capability

- Chassis intrusion

- Operating system (OS) hangs
– Auto-restart initial program load (IPL) power supply
– Automatic error retry or recovery
– Automatic server restart
– Automatic restart after power failure
– Built-in, menu-driven configuration programs
– Built-in, menu-driven SCSI configuration programs

(some models)
– Built-in, menu-driven setup programs
– Failover Ethernet support
– Menu-driven diagnostic programs on CD-ROM
– Monitoring support for temperature, voltage, and fan

speed
– Server management
– ServeRAID™ adapter support
– Standard advanced system management (ASM) PCI

adapter provides control for remote system

management
– Upgradable BIOS, diagnostics, ASM PCI adapter

microcode, and POST

6 Hardware Maintenance Manual: xSeries 200

– Wake on LAN® (WOL) capability
– Microsoft® Windows NT® failover support

v Serviceability features

– 24/7 customer support
– 3-year warranty (parts: three (3) years; labor: one (1)

year)
– Adaptec 29160 built-in self-test (BIST)
– Alert on LAN™ with optional IBM Ethernet adapter
– CD-ROM-based diagnostics
– Diagnostic support of Ethernet adapters
– Error codes and messages
– Processor serial number access
– Read-only memory (ROM) checksums
– Standard cables present detection
– Standby voltage for system management features

and monitoring
– System error logging (ASM PCI adapter)
– Vital product data (VPD) (includes serial number

information and replacement part numbers, stored in

nonvolatile memory, for easier remote maintenance)

Server controls and indicators

CD eject
button

CD-ROM drive
activity light

Diskette eject
button

Hard disk drive
activity light

Power-on
light

Power control
button

Diskette drive
activity light

Ethernet speed 100 Mbps

Ethernet transmit/
receive activity

CD-ROM drive activity light: When this light is on, it

indicates that the CD-ROM drive is in use.

Diskette eject button: Push this button to install or

remove a diskette from the drive.

Diskette drive activity light: When this light is on, it

indicates that the diskette drive is in use.

Chapter 2. General information 7

Hard disk drive activity light: When this light is on, it

indicates that the hard disk drive is in use.

Power-on light: This status indicator lights when you turn

on your server.

Power control button: Press this button to manually turn

the server on or off.

See “I/O connector locations” on page 72 for the location
of the input/output (I/O) connectors on the rear of the
server.

Turning on the server

After you plug one end of the server power cord into the
power supply outlet on the rear of the server, and the other
end of the power cord into an electrical outlet, the server
can start as follows:

v Yo u can press the power control button on the front of

the server to start the server.

v If the server is turned on and a power failure occurs, the

server will start automatically when power is restored.

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.

1

2

Turning off the server

You can turn off the server in any of the following ways:

v Yo u can press the power control button on the front of

the server. This starts an orderly shutdown of the
operating system, if this feature is supported by your
operating system, and places the server in standby
mode.

Note: After turning off the server, wait at least five

seconds before you press the power control
button to turn on the server again.

8 Hardware Maintenance Manual: xSeries 200

v Yo u can press and hold the power control button for

more than four seconds to cause an immediate
shutdown of the server and place the server in standby
mode. Yo u can use this feature if the operating system
stops functioning.

v Yo u can disconnect the server power cords from the

electrical outlets to shut off all power to the server.

Note: After disconnecting the power cords, wait

approximately 15 seconds for your system to
stop running.

Chapter 2. General information 9

10 Hardware Maintenance Manual: xSeries 200

Chapter 3. Diagnostics

This section provides basic troubleshooting information to
help you resolve some common problems that might occur
with the server.

If you cannot locate and correct the problem using the
information in this section, refer to Chapter 7,
“Symptom-to-FRU index,” on page 99 for more information.

Diagnostic tools overview

The following tools are available to help you identify and
resolve hardware-related problems:

v POST beep codes

The power-on self-test (POST) generates beep codes
and messages to indicate successful test completion or
the detection of a problem. See “POST” for more
information.

v Diagnostic programs and error messages

The server diagnostic programs are provided on the IBM

Enhanced Diagnostics CD. These programs test the

major components of the server. See “Diagnostic
programs and error messages” on page 13 for more
information.

POST

When you turn on the server, it performs a series of tests
to check the operation of server components and some of
the options installed in the server. This series of tests is
called the power-on self-test or POST.

If POST finishes without detecting any problems, the first
window of the operating system or application program
appears.

Note:

1. If you have a power-on password or
administrator password set, you must type the
password and press Enter, when prompted,
before POST will continue.

2. A single problem might cause several error
messages. When this occurs, work 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 not occur the
next time you run the test.

© Copyright IBM Corp. 2000 11

POST beep code descriptions

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 99“.

POST error messages

The possible types of beep codes that your system might
emit are:

Repeating long beeps

Indicates that a memory error has occurred.
Ensure that all DIMMs are correctly installed.

One long beep and two short beeps

Indicates that a video error has occurred and the
BIOS cannot initialize the video screen to display
any additional information. Ensure that the video
adapter is correctly installed.

For

a list of POST errors, see “POST error codes” on page

110.

Small computer system interface
messages (some models)

The following table lists actions to take if you receive a
SCSI error message.

Note: If the server does not have a hard disk drive, ignore

any message that indicates that the BIOS is not
installed.

You will get these messages only when running the SCSI
Select Utility.

12 Hardware Maintenance Manual: xSeries 200

Table 2. SCSI messages

SCSI
Messages Description

All One or more of the following might be causing the

problem.

v A failing SCSI device (adapter or drive)
v An improper SCSI configuration
v Duplicate SCSI IDs in the same SCSI chain
v An improperly installed SCSI terminator
v A defective SCSI terminator
v An improperly installed cable
v A defective cable

Action:

Verify that:

v The external SCSI devices are turned on.

External SCSI devices must be turned on before
the server.

v The cables for all external SCSI devices are

connected correctly.

v The last device in each SCSI chain is

terminated properly.

v The SCSI devices are configured correctly.

If

the above items are correct, run the diagnostic

programs to obtain additional information about the
failing device.

Diagnostic programs and error
messages

The server diagnostic programs are stored on the IBM
Enhanced Diagnostics CD. These programs provide the
primary methods of testing the major components of 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 of complex problems that
are 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.

The following sections contain the error codes that might
appear in the detailed test log and summary log when
running the diagnostic programs.

Chapter 3. Diagnostics 13

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 089 is for the
microprocessor.

ttt is the three-digit failure code that

indicates the exact test failure that was
encountered.

iii is the three-digit device ID.

date is the date that the diagnostic test was

run and the error recorded.

cc is the check digit that is used to verify

the validity of the information.

text message is the diagnostic message that

indicates the reason for the problem.

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) given in the previous list.

Result can be one of the following:

Passed This result occurs when the diagnostic

test completes 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 server
configuration.

14 Hardware Maintenance Manual: xSeries 200

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.

Test

Specific String

This is additional information that is used to
analyze the problem.

Starting the diagnostic programs

The IBM Enhanced Diagnostics programs will isolate your
server hardware from software that you have installed on
your hard disk drive. The programs run independently of
the operating system, and must be run either from the 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.
You can also download the latest image of the diagnostics
from the World Wide Web at http://www.ibm.com/pc/
support.

Using the diagnostics CD

To start the IBM Enhanced Diagnostics using the CD, do
the following:

1. Turn off your server and any peripheral devices.

2. Turn on all attached devices; then, turn your 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.

Chapter 3. Diagnostics 15

Important

When you finish running the diagnostics and utilities, remove the
CD from the CD-ROM drive and turn off the server. You must
restore the First Startup Device to the original setting. Use steps
2 through 8 of this procedure to do this.

Downloading the diagnostics program

Do the following to download the latest image of the IBM
Enhanced Diagnostics from the World Wide Web and
create a startable Enhanced Diagnostics diskette:

1. Go to the following World Wide Web site:
http://www.ibm.com/pc/support/

2. Download the diagnostics file for your 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 in diskette drive A.

5. Type in the following, and then press Enter: filename a:
where filename is the name of the file you downloaded
from the Web.

The

downloaded file is self-extracting and will be copied to

the diskette. When the copy completes, you have a
startable IBM Enhanced Diagnostics diskette.

Using the diagnostic diskette

Do the following to start the IBM Enhanced Diagnostics
using the diagnostics diskette, do the following:

1. Turn off your server and any peripheral devices.

2. Insert the IBM Enhanced Diagnostics diskette into the
diskette drive.

3. Turn on all attached devices; then, turn on the server.

4. Follow the instructions on the screen.

5. Place the IBM Enhanced Diagnostics CD in the
CD-ROM drive. The diagnostics will load. Follow the
instructions on the screen to run the diagnostics.

When the tests have completed, you can view the Test Log
by selecting Utility from the top of the screen.

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.

16 Hardware Maintenance Manual: xSeries 200

Viewing the test log

The test log records data about system failures and other
pertinent information. The test log will not contain any
information until after the diagnostic program has run.

Note: If you already are running the diagnostic programs,

begin with step 4

1. Insert the IBM Enhanced Diagnostics CD.

2. Turn on the system and watch the screen.
If the system is on, shut down your operating system

and restart the system.

3. If a power-on password is set, the system prompts you
for it. Type in the appropriate password; then, press
Enter.

4. Run the appropriate diagnostics program and when the
Diagnostic Programs screen appears, select Utility.

5. Select View Test Log from the list that appears; then,
follow the instructions on the screen.

6. Yo u can save the test log to a file on a diskette or to
your hard disk drive.

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.

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 103. If diagnostic error messages
appear that are not listed in those tables, make sure that
the server has the latest levels of BIOS, Advanced System
Management Processor, ServeRAID, and diagnostics
microcode installed.

Power checkout

Power problems can be difficult to troubleshoot. For
instance, a short circuit can exist anywhere on any of the
power distribution busses. Usually a short circuit will cause
the power subsystem to shut down because of an
overcurrent condition.

A general procedure for troubleshooting power problems is
as follows:

1. Power off the server and disconnect the AC cord(s).

2. Check for loose cables in the power subsystem. Also
check for short circuits, for instance if there is a loose
screw causing a short circuit on a circuit board.

Chapter 3. Diagnostics 17

3. Remove adapters and disconnect the cables and
power connectors to all internal and external devices
until server is at minimum configuration required for
power on (see ″Minimum operating requirements″ on
page 117).

4. Reconnect the AC cord and power on the server. If the
server powers up successfully, replace adapters and
devices one at a time until the problem is isolated. If
server does not power up from minimal configuration,
replace FRUs of minimal configuration one at a time
until the problem is isolated.

To use this method it is important to know the minimum
configuration required for a server to power up (see page

117).

Recovering BIOS

If the BIOS has become corrupted, such as from a power
failure during a flash update, you can recover the BIOS
using the boot block jumper and a BIOS flash diskette. The
boot block jumper selects which of two BIOS images to
use. In the normal position, the jumper will be installed on
pins 2 and 3. In the alternate block position, the jumper will
be installed on pins 1 and 2.

Note: Yo u can obtain a BIOS flash diskette from one of

the following sources:

v Use the ServerGuide program to make a BIOS

flash diskette.

v Download files to make a BIOS flash diskette

from the World Wide Web. Go to
http://www.pc.ibm.com/support/ select IBM
System Support, and then make the selections
for your system.

Do

the following to recover the BIOS:

1. Turn off the server and peripheral devices and
disconnect all external cables and power cords; then,
remove the side cover, see “Removing the side cover”
on page 46.

2. Locate jumper JROM1 on the system board.

18 Hardware Maintenance Manual: xSeries 200

CMOS jumper
(JBAT1)

Boot block jumper
(JROM1)

1

1

2

2

3

3

3. Move the JROM1 jumper to the alternate position
(pins 1 and 2) to enable the BIOS recovery mode.

4. Reinstall the side cover, see “Installing the cover” on
page 70.

5. Reconnect all external cables and power cords and
turn on the peripheral devices.

6. Insert the BIOS flash diskette in the diskette drive.

7. Restart the server. The BIOS begins the power-on
self-test.

8. Select 1 - Update POST/BIOS from the menu that
contains various flash (update) options.

9. When prompted as to whether you want to save the
current code to a diskette, select N.

10. When prompted to choose a language, select a
language (from 0 to 7) and press Enter to accept your
choice.

11. Do not restart your server at this time.

12. Remove the BIOS flash diskette from the diskette
drive.

13. Turn off the server and peripheral devices and
disconnect all external cables and power cords; then,
remove the side cover, see “Removing the side cover”
on page 46.

14. Move the JROM1 jumper to the normal position (pins
2 and 3) to return to normal startup mode.

15. Reinstall the side cover, see “Installing the cover” on
page 70.

Chapter 3. Diagnostics 19

16. Reconnect all external cables and power cords and
turn on the peripheral devices.

17. Restart the server, which should start up normally.

Clearing CMOS

If you need to erase configuration information, you must
move the CMOS jumper. See the illustration in “Recovering
BIOS” on page 18 for the location of the CMOS jumper.

The default position is a jumper installed on pins 1 and 2.
Before you change the position of this jumper, you must
turn off the server and peripheral devices, and disconnect
all external cables and power cords. Remove the cover
and then move the jumper to pins 2 and 3.

After moving the jumper, wait at least 5 minutes for the
CMOS information to clear.

Changing the position of this jumper erases all
configuration and setup information, including the power-on
and administrator passwords. Therefore, you must
reconfigure the server after clearing CMOS memory (see
Chapter 4, “Configuring the server,” on page 33). If
possible, record your server configuration information

before moving the CMOS jumper.

After you clear the CMOS information, move the jumper
back to its normal position (pins 1 and 2). Reconnect the
external cables and power cords; then, turn on the
peripheral devices and the server.

Replacing the battery

When replacing the battery, you must replace it with a
lithium battery of the same type from the same
manufacturer. To avoid possible danger, read and follow
the safety statement below.

To order replacement batteries, call 1-800-772-2227 within
the United States, and 1-800-465-7999 or 1-800-465-6666
within Canada. Outside the U.S. and Canada, call your
IBM reseller or IBM marketing representative.

Note: After you replace the battery, you must reconfigure

your system and reset the system date and time.

20 Hardware Maintenance Manual: xSeries 200