IBM xSeries 200, xSeries 200VL, xSeries 200 8479, xSeries 200VL 8481 Hardware Maintenance Manual

򔻐򗗠򙳰

xSeries 200 Type 8479 and xSeries 200VL Type 8481

Hardware Maintenance Manual

򔻐򗗠򙳰

xSeries 200 Type 8479 and xSeries 200VL Type 8481

Hardware Maintenance Manual

Note

Before using this information and the product it supports, read “Notices” on page 137.

Third Edition (August 2008)
The following paragraph does not apply to the United Kingdom or any country where such provisions are

inconsistent with local law:

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.

© Copyright International Business Machines Corporation 2001. 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 xSeries 200™ Type 8479 server and xSeries 200VL Type 8481 server.

Important: This manual is intended for trained servicers who are familiar with

IBM PC Server products. Before servicing an IBM product, be sure to
review “Safety information” on page 103.

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.

© Copyright IBM Corp. 2001 iii

Lesen Sie alle Sicherheitshinweise, bevor Sie eine Anweisung ausführen.

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, Device
Driver files and documents.

The Web address is:

http://www.ibm.com/pc/support

iv xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Contents

About this manual . . . . . . . . . . iii

Important safety information . . . . . . . . iii

Online support . . . . . . . . . . . . .iv

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

General information . . . . . . . . .3

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

Server features . . . . . . . . . . . . . .4

Notices and statements used in this book . . . . .5

Reliability, availability, and serviceability . . . . .5

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

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

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

Diagnostics . . . . . . . . . . . . .9

Diagnostic tools overview . . . . . . . . . .9

POST . . . . . . . . . . . . . . . . .9

POST beep code descriptions . . . . . . . .9

POST error messages . . . . . . . . . .9

Small computer system interface messages (some

models) . . . . . . . . . . . . . . . .10

Diagnostic programs and error messages . . . .10

Text messages . . . . . . . . . . . .11

Starting the diagnostic programs . . . . . .12

Using the diagnostics CD . . . . . . . .12

Creating a diagnostics diskette from the CD 12
Downloading the diagnostics program . . .12

Using the diagnostic diskette . . . . . .13

Viewing the test log . . . . . . . . . .13

Diagnostic error message tables . . . . . . .13

Power checkout . . . . . . . . . . . . .14

Recovering BIOS . . . . . . . . . . . .14

Clearing CMOS . . . . . . . . . . . . .15

Replacing the battery . . . . . . . . . . .15

Temperature checkout . . . . . . . . . . .17

Diagnosing errors . . . . . . . . . . . .17

Troubleshooting the Ethernet controller . . . . .17

Network connection problems . . . . . . .17

Ethernet controller troubleshooting chart . . .18

Ethernet controller messages . . . . . . . . .19

Novell NetWare or IntraNetWare system ODI

driver teaming messages . . . . . . . . .19

NDIS 4.0 Windows driver messages . . . . .21

Ethernet teaming messages: . . . . . . . .22

Configuration . . . . . . . . . . . .25

Using the Configuration/Setup Utility program . .25

Starting the Configuration/Setup Utility program 25

Choices available from the Configuration/Setup

main menu . . . . . . . . . . . . .26

Using passwords . . . . . . . . . . .28

Using the SCSISelect utility program (some models) 28

Starting the SCSISelect utility program . . . .28

Choices available from the SCSISelect menu . .29

Using the PXE Boot Agent Utility program . . . .31

Starting the PXE Boot Agent Utility program . .31
Choices available from the PXE Boot Agent

Utility menu . . . . . . . . . . . . .31

Using the ServerGuide CDs . . . . . . . . .32

Features at a glance . . . . . . . . . .32

Setup and configuration overview . . . . . .34

System partition . . . . . . . . . . . .35

Typical NOS installation . . . . . . . . .35

Setting up or updating multiple servers . . . .35

Installing the NOS without ServerGuide . . . .36

Additional programs included with ServerGuide 36

Installing options . . . . . . . . . .37

Major components of the xSeries 200 . . . . . .37

System and PCI extender board . . . . . .37

System and PCI extender board options

connectors . . . . . . . . . . . . .37

System board internal cable connectors . . .38

System board external connectors . . . . .39

System board jumpers . . . . . . . . .39

Before you begin . . . . . . . . . . . .40

Working inside the server with the power on . .40

System reliability considerations . . . . . .40

Stabilizing feet . . . . . . . . . . . . .41

Side cover removal . . . . . . . . . . . .42

Bezel removal . . . . . . . . . . . . .43

Removing the support bracket assembly . . . . .45

Working with adapters . . . . . . . . . .46

Adapter considerations . . . . . . . . .46

Adapter installation . . . . . . . . . .47

SCSI or ServeRAID adapter installation . . . . .48

Internal drive installation . . . . . . . . . .49

Internal drive bays . . . . . . . . . . .50

Preinstallation steps (all bays) . . . . . . .51

Drive installation in bay 2 or 4 . . . . . . .51

Hard disk drive installation in bay 5, 6, or 7 . .53

Memory modules . . . . . . . . . . . .54

Microprocessor . . . . . . . . . . . . .56

Microprocessor removal . . . . . . . . .56

Microprocessor installation . . . . . . . .59

Installing a security U-bolt . . . . . . . . .61

Completing the installation . . . . . . . . .62

Installing the cover . . . . . . . . . . .62

Updating the server configuration . . . . . .63

Connecting external options . . . . . . . .64

I/O connector locations . . . . . . . . .64

Input/output connectors . . . . . . . . . .65

Mouse connector . . . . . . . . . . .66

Keyboard connector . . . . . . . . . .66

Parallel connector . . . . . . . . . . .67

Viewing or changing the connector

assignments . . . . . . . . . . . .67

Parallel connector . . . . . . . . . .67

© Copyright IBM Corp. 2001 v

Serial connectors . . . . . . . . . . . .68

Viewing or changing the serial-connector

assignments . . . . . . . . . . . .68

Serial connectors . . . . . . . . . . .68

Ethernet connector . . . . . . . . . . .69

Configuring the Ethernet controller . . . .69

High performance Ethernet modes . . . .69

Teaming mode . . . . . . . . . .69

Priority Packet mode . . . . . . . .70

Virtual LAN mode . . . . . . . . .71

Ethernet connector . . . . . . . . . .72

Universal Serial Bus connectors . . . . . . .72

USB cables and hubs . . . . . . . . .72

USB connectors . . . . . . . . . . .72

Audio connectors . . . . . . . . . . .73

Line out . . . . . . . . . . . . .73

Line in . . . . . . . . . . . . . .73

Mic . . . . . . . . . . . . . . .73

MIDI connector . . . . . . . . . . . .73

Video connector . . . . . . . . . . . .74

Ultra160 SCSI connector (some models) . . . .74

SCSI cabling requirements . . . . . . .74

Setting SCSI IDs . . . . . . . . . . .75

FRU information (service only) . . . .77

Hard disk drive cage . . . . . . . . . . .77

Power supply . . . . . . . . . . . . .78

Rear fan . . . . . . . . . . . . . . .79

System board . . . . . . . . . . . . . .79

CD-ROM drive . . . . . . . . . . . . .80

Floppy disk drive . . . . . . . . . . . .81

Button kit . . . . . . . . . . . . . . .82

Guide assembly / speaker . . . . . . . . .83

Bezel release latch . . . . . . . . . . . .84

Top/side cover . . . . . . . . . . . . .85

Handle assembly . . . . . . . . . . . .86

Adapter retainer . . . . . . . . . . . . .87

Symptom-to-FRU index . . . . . . .89

Beep symptoms . . . . . . . . . . . . .89

No beep symptoms . . . . . . . . . . . .90

Diagnostic error codes . . . . . . . . . . .90

Error symptoms . . . . . . . . . . . . .92

POST error messages . . . . . . . . . . .95

ServeRAID . . . . . . . . . . . . . .97

Undetermined problems . . . . . . . . . .97

Parts listing . . . . . . . . . . . .99

System . . . . . . . . . . . . . . . 100

Keyboards . . . . . . . . . . . . . . 101

Power cords . . . . . . . . . . . . . . 102

Related service information . . . . . 103

Safety information . . . . . . . . . . . . 103

General safety . . . . . . . . . . . . 103

Electrical safety . . . . . . . . . . . . 104

Safety inspection guide . . . . . . . . . 105

Handling electrostatic discharge-sensitive

devices . . . . . . . . . . . . . . 106

Grounding requirements . . . . . . . . 106

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

Send us your comments! . . . . . . . . . 136

Problem determination tips . . . . . . . . . 137

Notices . . . . . . . . . . . . . . . 137

Trademarks . . . . . . . . . . . . . . 138

vi xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

General checkout

The server 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 system board, Ethernet controller, video controller, RAM, keyboard,
mouse (pointing device), diskette drive, serial ports, hard drives, and parallel port.
You can also use them to test some external devices. See “Diagnostic programs and
error messages” on page 10.

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.

3. If the computer hangs with a POST error, go to the “Symptom-to-FRU index”

on page 89.

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

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

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

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

page 9.

© Copyright IBM Corp. 2001 1

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.

IF THE SYSTEM IS NOT PART OF A CLUSTER:

2.

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 messages” on page 95.

v Check the System Error Log. If an error was recorded by the system, see

“Symptom-to-FRU index” on page 89.

v Start the Diagnostic Programs. See “Diagnostic programs and error

messages” on page 10.

v Check for the following responses:

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

DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?

3.

NO. Find the failure symptom in “Symptom-to-FRU index” on page 89.

Run the Diagnostic Programs. If necessary, refer to “Diagnostic programs and

YES.

error messages” on page 10.

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

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

2 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

General information

The IBM xSeries 200 server delivers performance and affordability 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 bottom of
the server and on the lower-right side of the bezel. 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/eserver/xseries

Features and specifications

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

Model and
serial numbers

© Copyright IBM Corp. 2001 3

Table 1. Features and specifications

Microprocessor: Supports one
microprocessor (depending on your
model)
v Intel Pentium® III with 256 KB or

512 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: 128 MB
v Maximum: 1.5 GB
v Type: PC133 MHz, ECC SDRAM,

unregistered DIMMs

v Slots: Three dual inline

(depending on your model)

Drives:

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

Expansion

bays (depending on

model):

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

extender board

AGP

slot:

Power supply:

One 330 watt (90-240 V ac) Video:
ATI Rage XL

v 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 One 10BASE-T/100BASE-TX, Intel

Ethernet controller with Alert on
LAN™ and Wake on LAN

®

support

v Two serial ports
v 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: 5.1 bel

maximum

v Sound power, operating: 5.3 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%

output:

Heat

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.095 kVA
– Maximum: 0.470 kVA

Accelerated graphics port (AGP)
(contains the video adapter)

Server features

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

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

4 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

v Systems-management capabilities

See the documentation provided with your 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 enables simultaneous
transmission and reception of data on the Ethernet local area network (LAN).
These controllers support Alert on LAN 2 technology.

v IBM ServerGuide™ CDs

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

For more information about the ServerGuide CDs, see “Using the ServerGuide
CDs” on page 32.

Notices and statements used in this book

The caution and danger statements also appear in the multilingual safety book
provided on the IBM xSeries Documentation CD. Each statement is numbered for
easy reference to the corresponding statement in the safety book.

The notice and statement definitions are as follows:

v Notes: These notices provide important tips, guidance, or advice.
v Important: These notices provide information that might help you avoid

inconvenient or problem situations.

v Attention: These notices indicate possible 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 a 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.

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; that the server is available when you want
to use it; and that should a failure occur, you can easily diagnose and repair the
failure with minimal inconvenience.

The following is an abbreviated list of the RAS features that the server supports.
v Reliability features

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

General information 5

– ECC front-side buses (FSBs)
– ECC L2 cache
– ECC memory
– Parity checking on the small computer system interface (SCSI)
– Advanced configuration and power interface (ACPI)
– Power-on self-test (POST)
– SDRAM with serial presence detect (SPD)

Availability features

v

– Advanced desktop management interface (DMI) features
– 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
– Microsoft® Windows NT® failover support
– Monitoring support for temperature, voltage, and fan speed
– Server management
– ServeRAID™ adapter support
– Wake on LAN capability

v Serviceability features

– Adaptec 29160 built-in self-test (BIST)
– Alert on LAN 2
– CD-ROM-based diagnostics
– Diagnostic support of Ethernet adapters
– Error codes and messages
– Processor serial number access
– Read-only memory (ROM) checksums
– Vital product data (VPD) (includes serial number information and

replacement part numbers, stored in nonvolatile memory, for easier remote
maintenance)

6 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Server controls and indicators

This section identifies the controls and indicators on the front and rear of the
server.

Ethernet speed 100 Mbps

CD-eject
button

CD-ROM drive
activity light

Diskette-eject
button

Diskette drive
activity light

Hard disk drive
activity light

Power-on
light

Power-control
button

Ethernet transmit/
receive activity

CD-eject button: Push this button to open the CD tray to insert or remove a CD.

CD-ROM drive activity light: When this light is on, the CD-ROM drive is in use.

Diskette-eject button: Push this button to release a diskette from the drive.

Diskette drive activity light: When this light is on, the diskette drive is in use.

Ethernet speed 100 MBps: When this light is on, the Ethernet speed is 100 MBps.

When the light is off, the Ethernet speed is 10 MBps. The Ethernet speed light is
located on the Ethernet (RJ-45) connector on the rear of the server.

Ethernet transmit/receive activity: When this light is on, there is activity between
the server and the network. The Ethernet transmit/receive activity light is located
on the Ethernet (RJ-45) connector on the rear of the server.

Hard disk drive activity light: When this light is on, the hard disk drive is in use.

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

Power-control button: Press this button to manually turn the server on or off.

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

General information 7

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

Turning off the server

You can turn off the server in the following ways:

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

v You 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 5 seconds before you press the

power-control button to turn on the server again.

v You can press and hold the power-control button for more than 4 seconds to

cause an immediate shutdown of the server and place the server in standby
mode. You can use this feature if the operating system stops functioning.

v You 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.

8 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

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 “Symptom-to-FRU index” on page 89 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 10 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.

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

POST error messages

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

© Copyright IBM Corp. 2001 9

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.

a list of POST errors, see “POST error messages” on page 95.

For

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

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.

10 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

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.

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

Failed This result occurs when the diagnostic test discovers an error.
User Aborted

Not Applicable

This result occurs when the diagnostic test completes without any
errors.

This result occurs when you stop the diagnostic test before it is
complete.

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.

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.

Diagnostics 11

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 the 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 from
the 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 from the diagnostics CD, do the following:

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.

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.

Creating a diagnostics diskette from the CD: To create a diagnostics floppy
diskette from the CD, do the following:

1. Format a floppy diskette (or have a preformatted diskette available).

2. Boot the system from the diagnostics CD.

3. From the menu that appears, select Create diagnostic diskette.

4. Insert the formatted floppy diskette into the floppy disk drive when the

message on the screen prompts you to do so, and press Enter.

5. The diagnostics CD can then be removed and the system rebooted with the
newly created diskette.

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

12 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

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

the tests have completed, you can view the Test Log by selecting Utility

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

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 or diskette in the appropriate drive.

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

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 90. If diagnostic error

When you turn off the power to the server, the test log is cleared.

Diagnostics 13

Power checkout

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

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

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

Recovering BIOS

If the BIOS code has become damaged, such as from a power failure during a flash
update, you can recover the BIOS code using a BIOS flash diskette.

You 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 from the World Wide Web to make a BIOS flash diskette. Go to

Complete

1. When prompted, insert the BIOS flash diskette into the diskette drive.

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

3. The BIOS flash utility automatically starts.

4. When prompted as to whether you want to save the current code to a diskette,

5. When prompted, press Y to continue the flash process.

6. The system automatically starts the flash utility a second time.

7. When prompted as to whether you want to save the current BIOS code, stop

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

http://www.ibm.com/pc/support/ select IBM System Support, and then make
the selections for your system.

the following steps to recover the BIOS code:

select N.

the process by removing the BIOS flash diskette from the diskette drive.

14 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Clearing CMOS

If you need to erase configuration information, you must move the CMOS jumper.

1
2
3

CMOS jumper
(JBAT1)

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 “Configuration” on
page 25). If possible, record the 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.

Diagnostics 15

CAUTION:
When replacing the battery, use only IBM Part Number 33F8354 or an equivalent
type battery recommended by the manufacturer. If the server has a module
containing a lithium battery, replace it only with the same module type made by
the same manufacturer. The battery contains lithium and can explode if not
properly used, handled, or disposed of.

Do not:

v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble

Dispose

of the battery as required by local ordinances or regulations.

Do the following to replace the battery:

1. Read “Before you begin” on page 40, and follow any special handling and
installation instructions supplied with the replacement battery.

2. Turn off the server and peripheral devices and disconnect all external cables
and power cords; then, remove the server cover.

3. Remove the battery:
a. Use one finger to press the top of the battery clip away from the battery

until the battery releases upward from the socket.

b. Lift and remove the battery from the battery socket.

4. Do the following to insert the new battery:
a. Tilt the battery so that you can insert it into the socket under the battery

clip.

b. As you slide it under the battery clip, press the battery down into the

socket.

5. Reinstall the server cover and connect the cables.

6. Turn on the server.

7. Start the Configuration/Setup Utility program and set configuration

parameters.

v Set the server date and time.
v Set the power-on password.
v Reconfigure the server.

16 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Temperature checkout

Proper cooling of the server is important for proper operation and server reliability.
For a typical xSeries server, you should make sure:

v Each of the drive bays has either a drive or a filler panel installed
v Each of the power supply bays has either a power supply or a filler panel

installed

v The server cover is in place during normal operation
v There is at least 50 mm (2 inches) of ventilated space at the sides of the server

and 100 mm (4 inches) at the rear of the server

v The server cover is removed for no longer than 30 minutes while the server is

operating

v The processor housing cover covering the processor and memory area is

removed for no longer that ten minutes while the server is operating

v A removed hot-swap drive is replaced within two minutes of removal
v Cables for optional adapters are routed according to the instructions provided

with the adapters (ensure that cables are not restricting air flow)

v The fans are operating correctly and the air flow is good
v A failed fan is replaced within 48 hours

In addition, ensure that the environmental specifications for the server are met. See
“Features and specifications” on page 3.

Note: The speed of the fans will increase if:

v One fan fails.
v Ambient temperature gets too high.

Diagnosing errors

To find solutions to problems that have definite symptoms, see “Error symptoms”
on page 92.

If you cannot find the problem there, go to “Starting the diagnostic programs” on
page 12 to test the server.

If you have just added new software or a new option and the server is not
working, do the following before using the error symptoms table:

v Remove the software or device that you just added.
v Run the diagnostic tests to determine if the server is running correctly.
v Reinstall the new software or new device.

Troubleshooting the Ethernet controller

This section provides troubleshooting information for problems that might occur
with the 10/100 MBps Ethernet controller.

Network connection problems

If the Ethernet controller cannot connect to the network, check the following:
v Make sure that the cable is installed correctly.

The network cable must be securely attached at all connections. If the cable is
attached but the problem persists, try a different cable.

Diagnostics 17

If you set the Ethernet controller to operate at 100 MBps, you must use Category
5 cabling.

If you directly connect two workstations (without a hub), or if you are not using
a hub with X ports, use a crossover cable.

Note: To determine whether a hub has an X port, check the port label. If the

label contains an X, the hub has an X port.

v Determine if the hub supports auto-negotiation. If not, try configuring the

integrated Ethernet controller manually to match the speed and duplex mode of
the hub.

v Check the LAN activity light (if available) on the front of the server. The LAN

activity light illuminates when the Ethernet controller sends or receives data
over the Ethernet network. If the LAN activity light is off, make sure that the
hub and network are operating and that the correct device drivers are loaded.

v Make sure that you are using the correct device drivers, supplied with the

server.

v Check for operating server-specific causes for the problem.
v Make sure that the device drivers on the client and server are using the same

protocol.

v Test the Ethernet controller.

The way you test the Ethernet controller depends on which operating system
you are using (see the Ethernet controller device driver README file).

Ethernet controller troubleshooting chart

You can use the following troubleshooting chart to find solutions to 10/100 MBps
Ethernet controller problems that have definable symptoms.

Table 3. Ethernet troubleshooting chart

Ethernet controller
problem

The server stops
running when loading
device drivers.

The LAN activity light
(when available) does
not light.

Suggested Action

The PCI BIOS interrupt settings are incorrect.

Check the following:
v Determine if the IRQ setting assigned to the Ethernet controller

is also assigned to another device in the Configuration/Setup
Utility program.

Although interrupt sharing is allowed for PCI devices, some
devices do not function well when they share an interrupt with
a dissimilar PCI device. Try changing the IRQ assigned to the
Ethernet controller or the other device. For example, for
NetWare Versions 3 and 4 it is recommended that disk
controllers not share interrupts with LAN controllers.

v Make sure that you are using the most recent device driver

available from the World Wide Web.

v Run the network diagnostic program.
Check the following:

v Make sure that you have loaded the network device drivers.
v The network might be idle. Try sending data from this

workstation.

v Run diagnostics on the LEDs.

18 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Table 3. Ethernet troubleshooting chart (continued)

Ethernet controller

Suggested Action

problem

Data is incorrect or
sporadic.

Check the following:
v Make sure that you are using Category 5 cabling when

operating the server at 100 MBps.

v Make sure that the cables do not run close to noise-inducing

sources like fluorescent lights.

The Ethernet controller
stopped working when
another adapter was
added to the server.

Check the following:

v Make sure that the cable is connected to the Ethernet controller.
v Make sure that your PCI server BIOS is current.
v Reseat the adapter.
v Determine if the IRQ setting assigned to the Ethernet adapter is

also assigned to another device in the Configuration/Setup
Utility program.

Although interrupt sharing is allowed for PCI devices, some
devices do not function well when they share an interrupt with
a dissimilar PCI device. Try changing the IRQ assigned to the
Ethernet adapter or the other device.

The Ethernet controller
stopped working
without apparent
cause.

Check the following:

v Run diagnostics for the Ethernet controller.
v Try a different connector on the hub.
v Reinstall the device drivers. Refer to your operating system

documentation and to the ServerGuide information.

Ethernet controller messages

The integrated Ethernet controller might display messages from the following
device drivers:

v Novell NetWare™ or IntraNetWare system open data-link interface (ODI)
v Network driver interface specification (NDIS) adapter for level 4.0 (Windows

NT)

Novell NetWare or IntraNetWare system ODI driver teaming
messages

This section provides explanations of the error messages for the Novell NetWare or
IntraNetWare system ODI driver, and suggested actions to resolve each problem.

Table 4. NetWare driver messages for the Ethernet controller

Message Description

Couldn’t allocate resources. Explanation: An unknown error has occurred when trying

AFT group for primary
adapter in slot nnn already
exists.

to allocate needed resources for the AFT Module.

Action:

v Check the server configuration. If the problem persists,

contact your network supplier.

v Verify that the Ethernet controller is enabled. If the

Ethernet controller is enabled, run the diagnostic
programs.

Explanation: An attempt was made to rebind an adapter
already in an AFT group.
Action: Check the AFT slot numbers for existing AFT
teams. If the problem persists, contact your network
supplier.

Diagnostics 19

Table 4. NetWare driver messages for the Ethernet controller (continued)

Message Description

Error locating device control
table (DCT) addresses in
internal table. Make sure that
you have loaded LAN
drivers after loading
AFT.NLM.

Explanation: The bind command was entered prior to
loading the device driver. The device driver must be loaded
after loading AFT.NLM, but before any bind command can
be issued.
Action: Load the driver for the supported adapter and try
loading the AFT module again. If the problem persists,
contact your network supplier.

Insufficient number of
arguments specified.

Explanation: The appropriate or expected number of
parameters was not entered in a command.
Action: Check the parameters required for the given
command. If the problem persists, contact your network
supplier.

Duplicate slot numbers
detected.

Explanation: An attempt has been made to bind the same
slot number more than once.
Action: Check the slot numbers entered during the bind.
Adapter slot numbers must be valid and unique. If the
problem persists, contact your network supplier.

’xxx’ is not supported for
AFT team.

Explanation: A bind command has been issued for adapters
not supported by AFT.NLM.
Action: Make sure that you attempt to bind only adapters
supported by AFT.NLM.

Primary and Secondary
adapters do not match. AFT
group is not created.

Explanation: A bind command was entered for an adapter
team that is a combination of server and client adapters. An
AFT team must be a grouping of the same classification of
adapter.
Action: Verify that all the adapters bound in a team are of
the same classification.

Requested number of
Secondary cards are not
found.

Explanation: The number of adapters specified in the bind
command could not be located.
Action: Verify the numbers and slot locations of the
adapters to be bound. If the problem persists, contact your
network supplier.

Failed to create AFT group.
Make sure that the drivers
for supported adapters are
loaded, primary adapter is
bound to protocols, and

Explanation: Binding of protocol failed. Protocol is either
not bound to any adapter or is bound to more than one
adapter in the group.
Action: Ensure that the protocol is bound to only adapter in

an AFT team.
secondary adapter is not
bound to any protocols.

Error identifying slot
numbers for the specified
board names.

Explanation: The mapping between the board name entered

and the slot number for an adapter could not be

established.

Action: Check the board name for the adapter before

issuing the bind command. If the problem persists, contact

your network supplier.
Can’t unbind specified slot

from AFT group. Make sure
that the slot you specified is
for the primary adapter in an

Explanation: The number entered in the unbind command

was not the primary adapter in an AFT group.

Action: Reissue the unbind command and specify the slot

number for the primary adapter.
AFT group.

20 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Table 4. NetWare driver messages for the Ethernet controller (continued)

Message Description

LAN adapter at slot nnnn
(Port 0xaa) failed to reset.
Check the state of the
adapter.

Explanation: The adapter that you specified could not be
initialized.

Action:

1. Load the driver for the supported adapter.

2. Check that the adapter is seated properly in the slot and

try loading the AFT module again.

the problem persists, contact your network supplier.

If

AFT is not supported on this
version of NetWare™.

Explanation: The NetWare on the server is not a version
supported by AFT.
Action: Load and bind AFT only on supported versions of
NetWare (currently version 4.11 and above).

Failed to allocate resources
tags.

Explanation: An unknown error has occurred when trying
to allocate needed resources for the AFT module.
Action: Check server configuration. If the problem persists,
contact your network supplier.

Please unload all LAN
drivers before unloading
AFT.NLM.

Explanation: An attempt was made to unload the AFT.NLM
module before unloading the adapter driver.
Action: Unload the adapter driver before unloading the
AFT module.

NDIS 4.0 Windows driver messages

This section contains the error messages for the NDIS 4.0 drivers. The explanation
and recommended action are included with each message.

Table 5. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller

Error code
(hex) Description

0x00 Explanation: The driver could not register the specified interrupt.

Action: Using the Configuration/Setup Utility program, make sure that a

PCI interrupt is assigned to your Ethernet card, and that Ethernet is
enabled.

0x01 Explanation: One of the PCI cards did not get the required resources.

Action: Using the Configuration/Setup Utility program, make sure that a
PCI interrupt is assigned to your Ethernet card, and that Ethernet is
enabled.

0x02 Explanation: Bad node address (multicast address).

Action: Make sure the locally administered address is valid, if one is
specified. The address can not be a multicast address.

0x03 Explanation: Failed self-test.

Action: Make sure a cable is attached to the Ethernet connector.

0x0D Explanation: Could not allocate enough memory for transmit queues.

Action:

1. From the Windows NT desktop, select Start ” Control Panel ”
Networks ” Adapters.

2. Select your IBM Ethernet adapter from the list.

3. Select Properties ” Advanced.

4. Lower the resource values that apply to the transmit queue.

Diagnostics 21

Table 5. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet
controller (continued)

Error code
(hex) Description

0x0E Explanation: Could not allocate enough memory for receive queue.

Action:

1. From the Windows NT desktop, select Start ”Control Panel ”Networks
”Adapters.

2. Select your IBM Ethernet adapter from the list.

3. Select Properties ”Advanced.

4. Lower the resource values that apply to the receive queue.

0x0F Explanation: Could not allocate enough memory for other structures.

Action:

1. From the Windows NT desktop, select Start ” Control Panel ”
Networks ” Adapters.

2. Select your IBM Ethernet adapter from the list.

3. Select Properties ”Advanced.

4. Lower the value for the resource named in the message.

0x10 Explanation: Did not find any Ethernet controllers.

Action: Using the Configuration/Setup Utility program, make sure that

Ethernet is enabled.

0x11 Explanation: Multiple Ethernet controllers found, but none matched the

required ID.
Action: Using the Configuration/Setup Utility program, make sure that
Ethernet is enabled.

0x13 Explanation: Did not find any Ethernet controllers that matched the

required subven/subdev.
Action: Using the Configuration/Setup Utility program, make sure that
Ethernet is enabled.

0x16 Explanation: Single adapter found, but multiple instances tried to load.

Action: Using the Configuration/Setup Utility program, make sure that
Ethernet is enabled, and that the slot containing the IBM xSeries 200
10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI adapter is
enabled.

0x17 Explanation: Slot parameter not specified in the registry.

Action: Remove the adapter driver and reinstall it.

Ethernet teaming messages:

This section displays the messages associated with Ethernet teaming.

22 xSeries 200 Type 8479 and xSeries 200VL Type 8481: Hardware Maintenance Manual

Table 6. NDIS (Windows NT or Windows 2000) driver teaming messages for the Ethernet
controller

Event ID Type Description
01 Error Explanation: Team name and physical adapter name are

02 Error Explanation: Unable to allocate required resources.

the same. This is an invalid configuration.
Action: Reconfigure the adapter team by double-clicking
the PROSet icon in the control panel.

Action: Free some memory resources and restart.