XS 220
Table of contents
Loading...
Hardware Maintenance Manual
xSeries 220
IBM
Hardware Maintenance Manual
xSeries 220
IBM
Note:
Before using this info rm atio n and the produ ct it supp or ts , be sure to read th e gen era l
information under “Notices” on page 168.
Second Edition (F ebruary 2001)
The following paragraph does not apply to the United Kingdom or any country where such provisi ons are
incons istent 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 transactio ns, th erefore, 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 sho uld be made to your IBM reseller or IBM marketing
representative.
© Copyright International Business Machines C orporation 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplica tion or disclosure restrict ed by GSA ADP Schedule Contract with
IBM Corp.
About this manual
This manual contains dia gnost ic infor mat io n, a Symp tom -to- FR U index , servic e
information, error codes, error messages, and configuration information for the
xSeries 220.
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 befor e 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é crit es par les instruct ions.
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 operazi on e.
© Copyright IBM Corp. 2000 iii
Online support
Lea atentamente todas las declarac iones de pr ecaución y peligr o ante de llevar a cabo
cualquier operación.
Use the World Wide Web (WWW) to download Diagnostic, BIOS Flash, a nd Device
Driver files.
File download address is:
http://www.us.pc.ibm.com/files.html
IBM online addresses
The H M M manua l s online addres s 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
iv Hardware Maintenance Manual: xSeries 220
Contents
About this manual . . . . . . . . . . . . . . . . . . . iii
Important safety information . . . . . . . . . . . . . . . . . . . . . . iii
Online support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
IBM online addresses . . . . . . . . . . . . . . . . . . . . . . . . . . iv
General checkout. . . . . . . . . . . . . . . . . . . . . 1
General information. . . . . . . . . . . . . . . . . . . 3
Features and specifications . . . . . . . . . . . . . . . . . . . . . . . . 4
Server features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reliability, availability, and serviceability . . . . . . . . . . . . 6
Server controls and indicators. . . . . . . . . . . . . . . . . . . . . . 6
Starting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Turning off the server . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . 11
Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . . . . . 11
POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
POST beep codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
POST error messages. . . . . . . . . . . . . . . . . . . . . . . . . . 12
POST error log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Small computer system interface messages . . . . . . . . . 12
Diagnostic programs and error messages . . . . . . . . . . . 13
Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Starting the diagnostic programs . . . . . . . . . . . . . . . 14
Viewing the test log . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Diagnostic error messages . . . . . . . . . . . . . . . . . . . . . 15
Power checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Recovering BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Identifying problems using status LEDs . . . . . . . . . . . . 17
Front panel and system board LEDs. . . . . . . . . . . . . 18
Diagnostic LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Replacing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Temperature checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Diagnosing errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Troubleshooting the Ethernet controller. . . . . . . . . . 21
Ethernet controller messages . . . . . . . . . . . . . . . . . . . 23
Configuring the server . . . . . . . . . . . . . . . 29
Using the Configuration/Setup Utility program . . . . . 29
Starting the Configuration/Setup Utility program 30
Choices available from the Configuration/Setup main
menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Using passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Using the SCSISelect utility program. . . . . . . . . . . . . . . 35
Starting the SCSISelect utility program . . . . . . . . . . 35
Choices available from the SCSISelect menu . . . . . 37
Using the Preeboot eXecution Environment boot agent
utility program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Starting the PXE boot agent utility program . . . . . . 38
Choices avai l able from the PXE boot agent menu . 38
Tower-to-rack conversi o n . . . . . . . . . . . . . 41
Installing options. . . . . . . . . . . . . . . . . . . . 53
Major components of the xSeries 22 0 server. . . . . . . . . 54
System board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
System board options connectors . . . . . . . . . . . . . . . 55
System board internal cable connectors . . . . . . . . . . 55
System board external port connectors . . . . . . . . . . 57
System board jumpe rs an d sw it ch e s . . . . . . . . . . . . . 57
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
System reliability considerations. . . . . . . . . . . . . . . . 58
Rotating the stabilizing feet . . . . . . . . . . . . . . . . . . . . . . . 59
Removing the side cover . . . . . . . . . . . . . . . . . . . . . . . . . 59
Removing the bezel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Removing the support bracket assembly. . . . . . . . . . . . 61
Working with adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Adapter considerations . . . . . . . . . . . . . . . . . . . . . . . . 64
Installing an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Installing internal drives. . . . . . . . . . . . . . . . . . . . . . . . . . 67
Internal drive bays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Preinstallation steps (all bays) . . . . . . . . . . . . . . . . . . 69
Installing a drive in bay 1, 2, 3, or 4. . . . . . . . . . . . . . 69
Installing a non-hot-swap hard disk drive in bay 5, 6,
or 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Installing a hot-swap hard disk drive in bay 5, 6, or 7 .
72
Installing memory modules . . . . . . . . . . . . . . . . . . . . . . 76
Installing and removing a micropro cesso r . . . . . . . . . . 77
Installing a microprocessor. . . . . . . . . . . . . . . . . . . . . 78
Removing a microprocessor . . . . . . . . . . . . . . . . . . . . 82
Installing the bezel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Installing the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Connecting external options . . . . . . . . . . . . . . . . . . . . . . 84
Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . 84
I/O connector locations . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Input/Output ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Parallel port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Serial ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Universal Serial Bus ports. . . . . . . . . . . . . . . . . . . . . . 88
Keyboard port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Auxiliary-device (pointing device) port . . . . . . . . . . 90
Video port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
SCSI port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
FRU information (service only) . . . . . . . . 97
Button kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Hot-swap hard disk drive cage . . . . . . . . . . . . . . . . . . . . 98
Hot-swap backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Rear fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
System board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
CD-ROM drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Floppy disk drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Bezel release latch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Top/side cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Handle assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Adapter retainer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Symptom-to-FRU index. . . . . . . . . . . . . . 111
Beep symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
No beep symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Diagnostic error codes . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
POST error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Processor board LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ServeRAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
© Copyright IBM Corp. 2000 v
Undetermined problems . . . . . . . . . . . . . . . . . . . . . . . . 124
Parts listing . . . . . . . . . . . . . . . . . . . . . . . 127
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Keyboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Related service information . . . . . . . . . .133
Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Electrical safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Safety inspection guide . . . . . . . . . . . . . . . . . . . . . . . 135
Handling electrostatic dischar ge-sensitive devices 136
Grounding requirements. . . . . . . . . . . . . . . . . . . . . . 137
Safety notices (multi-lingual translations) . . . . . . . 137
Send us your comments! . . . . . . . . . . . . . . . . . . . . . . . . 167
Problem determination tips . . . . . . . . . . . . . . . . . . . . . . 168
Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
vi Hardware Maintenance Manual: xSeries 220
General checkout
The server diagnostic prog rams 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. You 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
softw a re, you ca n run the diagnostic programs t o confirm tha t the hard ware 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 par t of a shared DASD cluster (two or more systems sharing
the same external storage device(s)) . Prior to running diagnostics, verify that th e
failing system is not part of a shared DASD cluster.
A system might be part of a cluster if:
• The customer identifies the system as part of a cluster.
• 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.
• One or more sy stems are locate d 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 code s are displaye d, dia gno se the first error code disp layed.
3. If the computer hangs with a POST error, go to the “Symptom-to-FRU index” on
page 111.
4. If the computer hangs and no error is displayed, go to “Undetermined problems”
on page 124.
5. Power supply problems, see “Power checkout” on page 16 and “Symptom-toFRU index” on page 111.
6. Safety information, see “Safety information” on page 133.
7. Fo r in termitte nt pro b le ms , check the erro r l og; see “POS T error messag es ” on
page 12.
1. IS THE SYSTEM PART OF A CLUSTER?
© Copyright IBM Corp. 2000 1
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 SYSTE M IS NOT PART OF A CLUSTER :
• Power-off the computer and all external devices .
• Check all cables and power cords.
• Set all display controls to the middle position.
• Power-on all external devices.
• Power-on the computer.
• 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 119.
• Check the diagnostic LED panel system error LED; if on, see “Front panel and
system board LEDs” on page 18.
• Check the System Error Log. If an error was recorded by the system, see
“Symptom- to- F RU index” on page 111.
• Start the Diagnostic Programs. See “Diagn ostic programs and error
messages” on page 13.
• Check f or 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 “Symptom-to-FRU index” on page 1 11.
YES. Run the D ia g n o st ic program s. If necessary, refer to “D iagnostic p rog r a ms and
error me ssages” on page 13.
If you receive an error, go to“Symptom-to-FRU index” on page 1 11 .
If the diagnostics completed successfully and you still suspect a problem, see
“Undetermined problems” on page 124.
2 Hardware Maintenance Man ual: xSer ies 220
General inf ormation
Features and specifications . . . . . . . . . . . . . . . . . . . . 4
Server features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reliability, availability, and serviceability . . . . . . . . 6
The IBM®
xSeries 220® delivers great value for entry server appl ications. It
is ideally suited for networking environments that require superior microprocessor
performance, efficient memory management, flexibility, and large amounts of reliable
data storage.
The IBM xSeries 220 server comes with a three-y ear limited warranty and IBM Server
Start Up Support. If you have acce ss to the World Wide Web, you can obtain up-todate information about the server model and othe r IBM server products at the
following World Wide Web address: http://www.ibm.com/eserver/xseries/
Server controls and indicators . . . . . . . . . . . . . . . . . 6
Starting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
T urning off the server . . . . . . . . . . . . . . . . . . . . . . . . 9
Cover-release
latch
Key lock
© Copyright IBM Corp. 2000 3
Features and specifications
This section pro vides a summary of the features and specificat ions of the xSeries 220
server.
Microprocessor:
• Intel® Pentium® III microprocessor with MMX™ technology and SIMD
extensions
• 256 KB* ECC, level-2 cache (min.)
• 133 M Hz front - s i de b u s ( F S B )
• Support f or up to two microprocessors
Memory:
• Standard: 128 MB
• Maximum: 4 GB*
• Type: 133 MHz, ECC, SDRAM, registered DIMMs
• Slots: 4 dual in-line
Drives standard:
• Diskette: 1.44 MB
• CD-ROM: 48X IDE
• Supports hot-swap SCSI hard disk drives (some models)
1
*
Expa nsion bays:
• T w o 5.25-in. bays (one CD-ROM drive installed)
• Two 3.5-in. bays (one diske t te drive installe d )
• Three 3.5-in. slim bays available in drive cage (some models have a hard disk
drive installed)
PCI expansion slots:
• Th ree 33 M Hz/6 4- b i t
• Two 33 MHz/32-bit
Power suppl y:
One 330 watt autosensing (115-230 V ac)
Video:
• S3 vide o con tro ll er (integra ted on syste m b oard)
• Compatible with SVGA and VGA
• 8 MB SDRAM video memory
Size
• Height: 470 mm (18.5 in.)
• Depth: 508 mm (20 in.)
• Wi dth: 165 mm (6.5 in.)
• Weight: approximately 19.5 Kg (43 lb.) when fully configured or 15.9 Kg (35 lb.)
minimum
Integrated functions:
• Ultra160 SCSI low voltage differential (LVD) controller
• One 10BASE-T/100BASE-TX Intel Ethernet controller on the system board
• Two serial ports
• Parallel port
• T wo Universal Serial Bus (USB) ports
1. KB equals approximat ely 1000 bytes. MB equals approximately 1000000 bytes. GB equals appro ximately 1000000000 bytes.
4 Hardware Maintenance Man ual: xSer ies 220
• Keyboard port
• Mouse port
• IDE controller port
• Video port
Acoustical noise emissions:
• Sound power, idling: 5.9 bel maximum
• Sound power, operating: 6.1 bel maximum
Environment:
• 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 4 3º C (50.0º to 109. 4º F). M aximum alti tude : 2133 m (6998.0 f t)
• Humidity:
— Server on: 8% to 80%
— Server off: 8% to 80%
Heat output:
Approximate heat output in Britis h thermal u nits (Btu ) per hour
• Minimum configu r ation: 341 Btu (100 watt s)
• Maximum configurat i on : 1604 Btu (470 watts)
Server features
Electrical input:
• Sine-wave input (50-60 Hz) required
• Input voltage low ran ge:
— Minimum: 100 V ac
— Maximum: 127 V ac
• Input voltage high range:
— Minimum: 200 V ac
— Maximum: 240 V ac
• Input kilovolt-amperes (kVA), approximately:
— Minimum: 0.08 kVA
— Maximum: 0.52 kVA
The design of the server takes advantage of advancements in symmetric
multiprocessing (SMP), data storage, and memory management. The server
combines:
• Impressive performance using an innovative approach to SMP
The server supports up to two Pentium III microprocessors. The server comes
with one mic rop ro ces sor ins tall ed; y o u can i nst all an add ition al m icr o pr oc esso r to
enhance performance and provide SMP capability.
• Large sy stem memory
The me mo ry bus in th e se rver sup p or ts up to 4GB of sy s t e m memory. The
memory controller provides error correcting code (ECC) support for up to four
industry-standard PC133, 3.3 V, 168-pin, 8-byte, registered, synchronousdynamic-rando m a ccess memory ( SDRAM) dual inline memory modules
(DIMMs).
General information 5
• System-management capabilities
System-management software is included with the server to manage the
function s of the server loca lly and remot e ly. Refer to the documentation th at
comes with the system-management software for more information.
• 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 recep tion of data on the Ethernet local area network ( LAN).
• IBM ServerGuide™ CDs
The ServerGuide CDs that are in cluded wit h th e ser ver 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 pr ograms and device drivers. In addition, the
ServerGuide CDs include a variety of application programs for the server.
Reliability, availability, and serviceability
Three of the most important considerations in server design are reliability , availability ,
and serviceability (RAS). The RAS fact or s hel p to ensure the integrity of the data that
is stored on the server, the availability of the server when it is needed; and the ease
with which problems can be diagnosed and repaired.
The following is an abbreviated list of the RAS features that e server supports:
• Automatic restart after a power failure
• Cyclic redundancy check (CRC) checking on the small computer system interfa ce
(SCSI) buses
• Diagnostic light-emitting diodes (LEDs)
• Error checking and corr ecting (ECC) memory
• Error codes and messages
• Menu-driven setup, system configuration, redundant array of independent disks
(RAID) configuration (optional), and diagnostic programs
• Optional system-management adapter subsystem to provide control for remote
system management
• Optional Wake on LAN
adapter)
• Power and temperature monitoring
• Power-on self-test (POST)
• Proce ssor serial number access
• System error logging (POST)
• Upgradeable basic input/output system (BIOS) and diagnostics
• Vital product data (VPD) on memo ry, syste m b oard, and hot-swap drive
backplane
®
(WOL) function through network-interfa ce card (NIC
Server controls and indicators
This section identifies the controls and indicators on the front of the server.
6 Hardware Maintenance Man ual: xSer ies 220
CD-ROM
eject button
CD-ROM drive
activity light
Diskette-eject
button
Diskette drive
activity light
SCSI
activity light
Power-on
light
Power-control
button
System error
light
CD-ROM eject button: Press this b u tton to release a CD f rom the drive.
CD-ROM drive activity light: When this light is on, it indicates that the CD-R O M
drive is in use.
Diskette-eject button: Press this button to release a diskette from the drive.
Diskette-drive activity light: When this light is on, it indicates that the diskette drive
is in use.
SCSI activity light: When this green light is flashing, the controller is accessing a
SCSI device, for example, a hard disk drive.
Note: Hot-swap hard disk drives also have an activity light. This light is also known
as the SCSI hard disk drive activity light.
If the server has a ServeRAID™ controller installed and this light flashes slowly (one
flash per second), the drive is being rebuilt. When the light flashes rapidly (three
flashes per second), the controller is ident ifying th e driv e.
Power-on light: When this green light is on, system power is present in the server.
Power-control button: Press this bu t ton to man ually tur n the se rver on or off.
System error light: When this amber light is on, it indicates that a system error has
occurred. An amber error light on the interior of the server, adjacent to the faulty
component, will also be on to further isolate the error. (For more information, see
“Diagnostics” on page 11.)
Cover-release latch: Slide this lever to release the cover.
General information 7
Cover-release
latch
Starting the server
After you plug the power cord of your server into the power supply and an electrical
outlet, the server can start in any of the following ways:
• You can press the power-control button on the front of the server to start the
server.
Notes:
1. You can install a circular disk over the power-control button to prevent
accidental manual power-off. This disk, known as the power-control bu tton
shield, comes with your server .
2. After you plug the power cord of your server into an electrical outlet, wait
approximately 20 seconds before pressing the power-control button. During
this time, the system is initializing; therefore, the power-control button does
not respond.
• If the server is turned on and a power failure occurs, the server will start
automatically when power is restored.
• The Wake on LAN feature will turn on the server at the set time (when a Magic
Packet is received), provided that all of the following conditions are met:
— AC power is present.
— The server i s e ither off or shu t down from an Advanced Configuration and
Power Interface (ACPI) operating system.
Key lock
8 Hardware Maintenance Man ual: xSer ies 220
— The Wake on LAN featu re is enabled in the Configuration/Setup Utilit y
program.
— A supported Wake on LAN adapter is installed in PCI slot 1 and is connected
to the system board with the 3-pin auxiliary power connector.
Notes:
1. See “Choices available f r om the Conf igurati on/Setup main m enu” on page 30
for a description of the Config urat ion /Se tup Utilit y program .
2. See “System board option s connectors” on page 55 for connector locations.
3. For additional infor mation on the Wake on LAN function, adapters, and
cables, refer to the documentation that comes with the adapters.
4. See “Ethernet port” on page 93 for informati on on Ethernet controllers and
adapters, and Wake on LAN PCI adapters.
• If the optional system-mana gement adapter is installed in your server, the
system-management adapter can turn on the server.
CAUTION:
The power control butto n on the device and the power switch on the powe r supply do not
turn off the el ectr ica l curr ent suppl ied to t he dev ice. The devi ce also might have mor e than
one power cord. To remove all electri cal current from the device, ensure that all power
cords are disconnected from the power source.
Turning off the server
You can turn off the server in any of the following ways:
• You can press the power-control button on the top of the server. This starts an
orderly shutdown of the operating system, if this feature is supported by your
operating sy stem.
Note: After tu rning off the se rver, wait at least five seconds before you press the
powe r-c ontrol butto n to tu r n on the server ag a in .
• You might need to press and hold the power-control button for more than four
seconds to cause an immediate shutdown of the server and to force the power off.
You can use this feature if the operating system stops functioning.
• You can disconnect the server power cords from the electrical outlets to shut off
all power to the server.
Note: After di sconnecting the power cords, wait appr oximately 15 seconds for
your system to stop running. Watch for the p owe r-on light to stop
blinking.
General information 9
10 Hardware Maintenance Manual: xSeries 220
Diagnostics
Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . 11
POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
POST beep codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
POST error messages . . . . . . . . . . . . . . . . . . . . . . . . 12
POST error log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Small computer system interface messages . . . . . 12
Diagnostic programs and error messages . . . . . . . 13
Text messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Starting the diagnostic programs . . . . . . . . . . . . . . 14
Viewing the test log. . . . . . . . . . . . . . . . . . . . . . . . . . 15
Diagnostic error messages . . . . . . . . . . . . . . . . . . . . 15
This section provides basic troubleshooting information to help you resolve some
common pr oblems that might occur wi th the server.
If you cannot locate and correct the problem using the information in this sec tion,
refer to “Symptom-to-F RU index” on page 111 for more information.
Diagnostic tools overview
The following tools are available to help you identify and resolve hardware-related
problems:
• POST beep cod es , error me ss ages , and error l ogs
The power-on self-test (POST) generates beep codes and messages to indicate
successful test completion or the det e ction of a problem. See “POST” for more
information.
• Diagnostic programs and error messages
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. See “Diagnostic programs and error
messages” on page 13 for more informa ti on .
• Error symptoms
These charts list problem symptoms, along with suggested steps to correct the
problems. See “Diagnosing errors” on page 21 for more information.
• Diagnostic LEDs
The serve r has light-emi tting diodes (LE Ds) to help you iden tify problems with
server components. These LEDs are part of the diagnostics that are built into the
server. See “Diagnostic LEDs” on page 18 for more information.
Power checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Recovering BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Identifying problems using status LEDs. . . . . . . . 17
Front panel and system board LEDs . . . . . . . . . . . 18
Diagnostic LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Replacing the battery. . . . . . . . . . . . . . . . . . . . . . . . 19
T e mperature checkout . . . . . . . . . . . . . . . . . . . . . . . 20
Diagnosing errors. . . . . . . . . . . . . . . . . . . . . . . . . . . 21
T roubleshooting the Ethernet controller . . . . . . . . 21
Ethernet controller messages . . . . . . . . . . . . . . . . . 23
POST
When you turn on the server, it performs a series of tests to check the operation of
server components an d some of the options installed in th e se rver. This se ries of tests
is called the power-on self-test or POST.
If POST finishes without detecting any problems, a single beep sounds and the first
screen of the operating system or application program appears.
© Copyright IBM Corp. 2000 11
If POST detects a problem, more than one beep sounds and an error message appears
on the screen. See “POST beep codes” and “POST error messages” for more
information.
Notes:
1. If you have a power-on 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 fir st e rror 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 te s t .
POST beep codes
POST generates beep codes to indicate successful completion or the detection of a
problem.
• One beep indicates the successful completion of POST.
• More than one beep indicates that POST detected a problem. For more
information, see “Beep symptoms” on page 111.
POST error messages
POST error messages occur during startup when POST finds a problem with the
hardware or detects a change in the hardware configuration. For a list of POST
errors, se e “ P O S T error codes” on page 119.
POST error log
The POST error log contains the three most recent error codes and messages that the
syste m gener a te d du ring PO ST.
To view the contents of the error logs, start the Configuration/Setup Utility program
(see “Starting the Configuration/Setup Utilit y program” on page 30); then, sele ct
Error Logs from the main menu.
Small computer system interface messages
The following table lists actions to take if you receive a SCSI error message.
Note: If your 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 SCSISelect Utility.
12 Hardware Maintenance Manual: xSeries 220
SCSI Messages Description
All One or more of the following might be causing the problem.
• A failing SCSI device (adapter, drive, controller)
• An improper SCSI configuration
• Duplicate SCSI IDs in the same SCSI chain
• A n improperly installed SCSI terminator
• A defective SCSI terminator
• A n improperly installed cable
• A defectiv e cable
Action:
Verify that :
• The external SC SI devic es are turned on. Externa l SCSI de vices m ust
be turned on before the server.
• The cables for all external SCSI devices are connected correctly.
• The last device in each SCSI chain is termin ated prope r l y.
• The SCSI devices are co nfigured co r rectly.
If the above items are correct, run the diagnostic programs to obtain
additional information about the failing device. If the error remains or
recurs, call for service.
Table 1. SCSI messages.
Diagnostic programs and error messages
The server diagnostic prog rams 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.
Diagnostic error messages indicate that a problem exists ; they ar e not necess aril y
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.
Somet i m e s th e f i rs t e rro r to occur caus e s add i tional erro rs . In this case , the se r v er
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 thre e -digit fun ction code that in di cates the function being
tested when the error occurred. For example, function c od e 089 is for
the microprocessor.
ttt is the thre e -digit failure code that indicates the exact test failu re that
was encou ntered.
Diagnostics 13
iii is the thr e e-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 rea son for the problem .
Text messages
The diagnostic text message format is as follows:
Function Name: Result (test specific string)
where:
Func tion Name is the name of the function being tested when the err or occurre d. 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 com p letes
without any errors.
Failed This re sult occurs when the di agnostic te st discovers an error.
User Aborted
This r e su lt occurs when y ou s top the diagnosti c 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 syste m configurati on.
Warning This result occurs when a possible problem is rep orted
during the diagnostic test, such as when a device that is to be
tested is not installed.
Te st Spec i fi c Stri ng
This is additional information th at you can use to anal yz e the
problem.
Starting the diagnostic programs
You can press F1 while running the diagnostic programs to obtain Help information.
You also can press F1 from within a help screen to obtain online documentation f rom
which you can select different categories. To exit Help and return to where you left
off, press Esc.
To start th e di agnostic pr ograms:
1. Turn on the server and watch the screen.
2. When the message F2 for Diagnostics appears, press F2.
3. Type in the appropriate password; then, press Enter .
4. Select either Extended or Basic from the top of the screen.
5. When the Diagnostic Programs screen appears, select the test you want to run
from the list that appears; then, follow the instructi ons on the screen.
14 Hardware Maintenance Manual: xSeries 220
Notes:
a. If the server stops during testing and you cannot continue, restart the server
and try running the diagnostic programs again.
b. The keyboard and mouse (pointing device) tests assume that a keyboard and
mouse are attached to the server.
c. If you run the diagnostic programs with no mouse a tta ched to the server, you
will not be able to navigate between test categories using the Next Cat and
Prev Cat buttons. All other functions pro vided by mouse-sel e ctable buttons
are also available using the function keys.
d. You can run the USB interface test and the USB external loopback test only if
there are no USB devices attached.
e. You can view server configuration information (such as system configuration,
memory contents, interrupt request (IRQ) use, direct memory access (DMA)
use, device drivers, and so on) by selecting Hardware Info from the top of the
screen.
When the tests have completed, you can view the Test Log by selectin g 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.
Viewing the test log
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 3..
To view the test log:
1. Turn on the server and watch the screen.
If the server is on, shut down the operating system and restart the server.
2. When the message F2 for Diagnostics appears, press F2.
If a power-on password is set, the server prompts you for it. Type in the
appropriate password; then, press Enter.
3. When the Diagnostic Programs screen appears, select Utility from the top of the
screen.
4. Select View Test Log from the list that appears; then, follow the instructions on
the screen.
The system maintains the test-log data while the server is powered on. When you
turn off the power to the server, the test log is cleared.
Diagnostic error messages
For descriptions of the error messages that might appear when you run the diagnostic
programs, see “Diagnostic error codes” on page 115. If diagno stic error me ssages
appear that are not listed in those tables, make sure that the server has the latest levels
of BIOS, ServeRAID, and diagnostics microcode installed.
Diagnostics 15
Power checkout
Power problems can b e difficu lt to trou bleshoot. For instance, a short circui t can exist
anywhere on any of the power distribution bu sses. Usually a short circuit will cause
the power su b s ystem to shut d own because of an overcurrent conditi o n.
A general procedure for troubleshooting power problems is as follows:
1. Power off the system and disc onnect the AC cord(s).
2. Check for loose cables in the power subsystem. Also check for short circuits, for
3. Remove adapters and disconnec t th e cables and power connectors to all intern al
4. Reconnect the AC cord and power on the system. If the system powers up
To use this method it is important to know the minimum configuration required for a
system to power up (see page 125).
Recovering BIOS
instance if there is a loose screw causing a short circuit on a circuit board.
and external devices until system is at minimum configuration required for
power on (see "Minimum operating requirements" on page 125).
successfully, replace adapters and devices one at a time until the problem is
isolated. If system does not power up from minimal configuration, replace FRUs
of minimal configuration one at a time until the problem is isolated.
If the BIOS has become damaged, such a s from a power failure during a flash updat e,
you can recover the BIOS using the flas h ROM page-swa p jumper (J38) and a BIOS
flash diskette.
Note: You can obtain a BIOS flash diskette fr om one of the following sources:
• Use the ServerGuide program to make a BIOS flash diskette.
• Download a BI OS f lash diskette from the World Wide Web. Go to
http://www.ibm.com/pc/support/, select IBM Server Support, and
make the selections f o r your serve r.
The flash memory of your server consists of a primary page and a backup page. The
J38 jumper controls which page is used to start the server. If the BIOS in the primary
page is damaged, you can use the backup page to star t the server; then, start the BIOS
flash diskette to restore the BIOS to the primary page.
To rec ove r th e BIOS, do the f oll ow ing :
1. Turn off the server and peripheral devices and disconnect all external cables and
power cords; then, remove the cover.
2. Locate jumper J38 on the system board .
16 Hardware Maintenance Manual: xSeries 220
Switch block
Flash ROM
page-swap
jumper (J38)
3. Move J38 to the lo setting (pins 1 and 2) to enable BIOS recovery mode.
4. Reconnect all external cables and power cor ds and turn on the peripher al devices.
5. Insert the BIOS flash diskette in the diskette drive.
6. Restart the server. The system begins the power-on self-test (POST).
7. Select 1 - Update POST/BIOS from the menu th at contains vario u s fl ash (update)
options.
8. When prompted as to whether you want to save the current code to a diskette,
press N.
9. When prompt e d to choose a language , se lect a language (from 0 to 7) and pre ss
Enter to accept your choice.
10. Do not restart your system at thi s time.
1 1. Remove the BIOS flash diskette from the diskette drive.
12. Turn off the server.
13. Move jumper J38 to the hi setting (pins 2 and 3) to return to no rmal startup mode.
14. Restart the server.
Identifying problems using status LEDs
The serve r has diagnostic LEDs to help you identi f y problems with some server
components. Use the diagno stic LEDs to identify the f ailing or inco rrectly installe d
components.
Diagnostics 17
Front panel and system board LEDs
The server do e s not contain a diagnostic or informat ion panel. The system error LED
is on the front panel inside the server . All of the remaining error LEDs are on the
system board, adjacent to the failing components. See “Diagnostic LEDs” for
information on ident ifying p roblems using the se LED s.
The meanings of these LEDs are as follows:
CPU1 Microproce ssor number 1 (co nn e ctor U12) fault
CPU2 Microprocessor number 2 (co nne ctor U11) fault
Fan 1 Fan number 1 (connector J10) failure (see note 1)
Fan 2 Fan number 2 (connector J18) failure (see note 1)
MEM1 DIMM number 1 (connector J19) fault
MEM 2 DIMM number 2 (connector J21) fault
MEM 3 DIMM number 3 (connector J23) fault
MEM 4 DIMM number 4 (connector J26) fault
VRM1 Microprocessor VRM number 1 (connector J42) fault (see note 1)
VRM2 Microprocessor VRM number 2 (connector J12) fault (see note 1)
Notes:
1. The fan and VRM LEDs will illuminate only if the optional system management
adapter is installed in the server.
2. The server does not support user-replaceable power supplies or fans.
Diagnostic LEDs
You can use the diagnostic LEDs built into the server to quickly identify the type of
system error that occurred. The server is designed so that LEDs remain illuminated
when the server shuts down, as long as the power supply is operating properly. This
feature helps you to isolate the problem if an err or causes the server to shut down. To
correct specific problems, see “Symptom-to-FRU index” on page 111.
System Error LED (on the front panel) System board LED Cause
On
A system error was detected. Check to
see which of the LEDs on the system
board ar e o n .
On MEM1, MEM2 , MEM3, or MEM4
On CPU1 or CPU2 (system board) One of the microprocess ors ha s failed,
On Fan 1 or Fan 2 One of the fans has failed or is
On VRM1 or VRM2 (system board) One of the microprocessor VRMs has
None The system error log is 75% or more
full or a Predictive Failure Analysis
(PFA) alert was logged.
A memory error occurred.
(system board)
or a microprocessor is installed
incorrectly.
operating too slowly .
failed, or a microprocessor VRM is
installed in the wrong connector.
Table 2. Diagnostic LEDs.
18 Hardware Maintenance Manual: xSeries 220
System Error LED (on the front panel) System board LED Cause
On System error (front panel) The diagnostic LEDs have detected a
system error.
Off None The diagnostic LEDs have not
detected a system error.
Table 2. Diagnostic LEDs.
Replacing the battery
When replacing the battery you must replace it with a lithium battery of the same
type, from the same manufacture r. To avoid possible danger r e ad and follow the
safety statement below.
To order repl acement 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 the server and reset the
system date a nd time.
CAUTION:
When replacing the battery, use only IBM Part Number 33F8354 or an equivalent
type battery recommended by the manufacturer. If your system has a module
containing a lithium battery, replace it only with the same module type made by
the same manufacturer. The battery contains lithium and can explode if not
properly used, handled, or disposed of.
Do not:
• Throw or immerse into water
• Heat to more than 100°C (212° F)
• 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 58, and follow any special ha ndl ing 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 any PCI cards that might impede access to th e b a ttery.
4. Remove the battery:
a. Use one finger to lift the battery clip over the battery.
b. Use one finger to slightly slide the battery out from its socket. The spring
mechanism will push the battery out toward you as you slide it from the
socket.
c. Use your thumb and index finger to pull the battery from under the battery
clip.
Diagnostics 19
d. Ensure that the battery clip is touching the base of the battery socket by
pressing gently on the clip.
5. Insert the new battery:
a. Tilt the batt e ry so that you can insert it into the so cket, under the b a ttery clip.
b. As you slide it under the battery clip, press the battery down into the socket.
6. Reinstall the server cover and connect the cables.
7. Turn on the ser ver.
8. Start the Configuration/Setup Utility program and set configuration parameters.
• Set the system date and time.
• Set the power-on password.
• Reconfigure your server.
Temperat ur e checkou t
Proper cooling of the system is important for proper operation and system reliability.
For a typical IBM xS e r i e s se r v er, you sh ould make su re :
• Each of the drive bays has either a drive or a filler panel installed
• The cover is in place during normal operation
• There is at least 50 mm (2 inches) of ventilated space at th e sides of the server and
100 mm (4 inches) at the rear of the server
• The cover is removed for no longer than 30 minutes while the server is operating
• A removed hot-swap drive is replaced within two minutes of removal
• Cables for optional adapters are routed according to the instructions provided
with the adapters (ensure that cables are not restricting air flow)
• The fans are operati ng correctly and the air flow is good
• A failed fan is replaced within 48 hours
In addition, ensure that the environmental specifications for the system are met. See
“Features and specifications” on page 4.
20 Hardware Maintenance Manual: xSeries 220
Diagnosing errors
To find solutions to problems that have definite symptoms, see “Error symptoms” on
page 117.
If you cannot find the problem there, go to “Starting the diagnostic programs” on
page 14 to test the se rver.
If you ha ve jus t ad de d new soft ware or a n ew opt ion and the se rver i s not wo rkin g, d o
the following before using the error symptoms table:
• Remove the software or device that you just added.
• Run the diagnostic tests to determ ine if the server is runn ing correctly.
• 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 ca nnot connec t to the network, check the following:
• Make sure that the cable is installed correctly.
• Determine if the hub supports auto-negotiation. If not, try configuring the
• Check th e LAN a ctivity light on the front of the server. The LAN activity li ght
• Make sure that you are using the correct device drivers, supplied with your
• Check for operating system-specific causes for the problem.
• Make sure that the device drivers on the client and server are using the same
• Test the Ethernet controller.
The network cable must be securely attached at all connections. If the cable is
attached but the problem persists, try a different cable.
If you set the Ethernet contr oll er to operate at 100 Mbps, you must use Cate gory 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 whet her a hub has an X port, check the port label. If the label
contains an X, the hub has an X port.
integrated Ethernet controller manually to match the speed and duplex mode of
the hub.
illuminates whe n the Et hernet controller s ends or receive s data over th e Ether ne t
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.
server.
protocol.
How you test the Ethernet controll er 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 fi nd sol u ti ons to 10/100 Mbps
Ethernet controller problems that have definite symptoms.
Diagnostics 21
Ethernet controller
problem
The server stops
running when loading
device drivers.
The LAN activity light
does not light.
Suggested Action
The PCI BIOS interrupt settings are incorrect.
Check the following:
• Determine if the interrupt (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 functi on well wh en the y share an interr up t with
a dissimilar PCI device. Try changing the IRQ assigned to the
Ethernet controller or the other device. For exa mple, for
NetWare V ers i ons 3 and 4 it is recommended that di sk
controllers not share interrupts with LAN controllers.
• Make sure that you ar e using the most r ecent device driver
available from the World Wide Web.
• Run the netwo rk diag n osti c progra m .
If the problem remains, call for service.
Check the following:
• Make sure that you have loaded the network device drivers.
• The network might be idle. Try sending data from this
workstation.
• Run diagnostics on the LEDs.
• The function of this LED can be changed by dev i ce driver load
parameters. If necessary, remove any LED parameter settings
when you load the device drivers.
Data is incorrect or
sporadic.
The Ethernet
controller stopped
working when
another adapter was
added to the server.
Check the following:
• Make sure that you are using Category 5 cabling when
operating the server at 100 Mbps.
• Make sure that the cables do not run close to noise-indu cing
sources like fluorescent lights.
Check the following:
• Make sure that the cable is connected to the Ethern et controller.
• Make sure that your PCI system BIOS is curr ent .
• Reseat the adapter.
• Determine if the interrupt (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 functi on well wh en the y share an interr up t with
a dissimilar PCI device. Try changing the IRQ assigned to the
Ethernet adapter or the other device.
If the problem remains, call for service.
Table 3. Ethernet troubleshooting cha rt.
22 Hardware Maintenance Manual: xSeries 220
Loading...