IBM xSeries 300 Hardware Maintenance Manual
Hard ware Mainte n ance Man u al
xSeries 300
Hard ware Mainte n ance Man u al
xSeries 300
Note
Before using this information and the product it supports, be sure to read the general information under “Notices” on
page 109.
First Edition (May 2001) (Updated February 2002)
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 2000. 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
Important: This manual is intended for trained servicers who are familiar with
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.
xSeries 300 server.
IBM PC Server products.
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. 2000 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
IBM Online Addresses
Use the World Wide Web (WWW) to download Diagnostic, BIOS Flash, and Device
Driver files.
File download address is:
http://www.us.pc.ibm.com/files.html
The HMM manuals online address is:
http://www.us.pc.ibm.com/cdt/hmm.html
The IBM PC Company Support Page is:
http://www.us.pc.ibm.com/support/index.html
The IBM PC Company Home Page is:
http://www.pc.ibm.com
iv Hardware Maintenance Manual: xSeries 300
Contents
About this manual ..........iii
Important safety information ........iii
Online Support .............iv
IBM Online Addresses ..........iv
Chapter 1. General checkout ......1
Chapter 2. General information .....3
Features and specifications..........4
What the IBM xSeries 300 offers ........5
Reliability, availability, and serviceability features . . 6
Servercontrolsandindicators ........7
Frontview..............7
Rearview..............8
Turning on the server ..........9
Turning off the server ..........9
Standby mode ............10
Chapter 3. Diagnostics ........11
Diagnostic tools overview .........11
POST ................11
POST beep code descriptions .......11
POST error messages ..........11
Small computer system interface messages (some
models)................12
Diagnostic programs and error messages ....12
Textmessages ............13
Starting the diagnostic programs ......14
Using the diagnostics CD........14
Downloading the diagnostics program . . . 14
Using the diagnostic diskette ......15
Viewing the test log ..........15
Diagnostic error message tables.......15
Power checkout .............16
Recovering BIOS code ...........17
ClearingCMOS.............19
Replacing the battery ...........19
Temperature checkout ...........21
Diagnosing errors ............21
Troubleshooting the Ethernet controller .....22
Network connection problems .......22
Ethernet controller troubleshooting chart . . . 22
Ethernet controller messages.........24
Novell NetWare or IntraNetWare system ODI
driverteamingmessages.........24
NDIS 4.0 (Windows NT) driver messages . . . 25
Ethernetteamingmessages:........27
Chapter 4. Configuring the server . . . 29
Starting the utility programs.........30
Using the Configuration/Setup Utility program 30
Starting the Configuration/Setup Utility
program.............30
Using the SCSISelect utility program (some
models)...............30
Starting the SCSISelect utility program . . . 30
Using the PXE boot agent utility program . . . 31
Starting the PXE boot agent utility program 31
UsingtheServerGuideCDs........32
ServerGuidestartupproblems.......33
Chapter 5. Installing Options .....35
Major components of the xSeries 300 server . . . 36
Before you begin ............36
Working inside the server with the power on . . 37
System reliability considerations ......37
Handling static-sensitive devices ......37
Removingthecover...........38
System board ..............39
System board internal cable connectors .....40
System board jumpers ...........41
Working with adapters ..........41
Adapter considerations .........42
Installing an adapter ..........42
Harddiskdrives ............44
Installing or replacing a hard disk drive ....44
WorkingwithDIMMs...........45
Installing DIMMs ...........45
Replacing the fan assembly .........47
Removing and installing a microprocessor ....47
Removing a microprocessor ........49
Installing a microprocessor ........51
Installing the cover ............53
Workingwithcables...........54
Chapter 6. FRU information (service
only)................55
Diskette/CD-ROM drives..........55
Diskette/CD-ROM drive bracket .......56
Power supply - AC ............57
Power supply - DC ............57
Beforeyoubegin ...........57
Wiring the – 48 V dc power connection to the
power supply ............57
Single input instructions ........58
Dual input instructions ........60
Disconnecting the DC Power Connection ....60
PCI riser card..............61
System board ..............62
Chapter 7. Symptom-to-FRU index . . . 63
Beepsymptoms.............63
Nobeepsymptoms............63
Diagnostic error codes ...........63
Errorsymptoms.............66
POST error codes ............69
ServeRAID ..............70
Undetermined problems ..........70
© Copyright IBM Corp. 2000 v
Chapter 8. Parts listing ........71
Keyboards...............72
Powercords.............73
Chapter 9. Related service information 75
Safety information ............75
General safety ............75
Electrical safety ............76
Safety inspection guide .........77
Handling electrostatic discharge-sensitive devices 78
Grounding requirements .........79
Safety notices (multi-lingual translations) . . . 79
Send us your comments! .........108
Problem determination tips.........109
Notices ...............109
Trademarks..............110
vi Hardware Maintenance Manual: xSeries 300
Chapter 1. General checkout
The server diagnostic programs are stored on CD-ROM. 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, and hard drives. You can also use them to test some
external devices. See “Diagnostic programs and error messages” on page 12.
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. Safety information, see “Safety information” on page 75.
2. 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.
3. If multiple error codes are displayed, diagnose the first error code displayed.
4. If the computer hangs with a POST error, go to “POST error codes” on page 69.
© Copyright IBM Corp. 2000 1
2 Hardware Maintenance Manual: xSeries 300
Chapter 2. General information
The IBM
®
xSeries 300 server is a one U-high1rack-model server for
high-volume network transaction processing. This high-performance server is
ideally suited for networking environments that require superior microprocessor
performance, efficient memory management, flexibility, and reliable data storage.
The xSeries 300 server comes with a three-year limited warranty and IBM Server
Start Up Support. If you have access to the World Wide Web, you can obtain
up-to-date information about your xSeries 300 model and other IBM server
products at the following World Wide Web addresses:
http://www.ibm.com/eserver/xseries
http://www.ibm.com/
1. Racks are marked in vertical increments of 1.75 inches each. Each increment is referred to as a unit, or a ″U″. A one-U-high device
is 1.75 inches tall.
© Copyright IBM Corp. 2000
3
Features and specifications
The following table provides a summary of the features and specifications for your
xSeries 300.
Microprocessor:
Supports either of the two listed
microprocessors (depending on your
model)
v One Intel
KB* Level-2 cache and MMX
®
Pentium®®III with 256
™™
(MMX2) technology
or
v One 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 only
v Slots: Three dual inline
v Supports 128, 256, and 512 MB
DIMMs
Drives:
v Diskette: 1.44 MB
v CD-ROM: 24X IDE
v Supports up to two hard disk
drives
Expansion bays:
Two 3.5-in. slim-high bays for hard
disk drives
PCI expansion slots:
Two 33 MHz/32-bit on the system
board
Power supply:
200 watt (110 or 220 V ac
auto-sensing) with Wake on LAN
support
Video:
v S3 Savage 4 Pro video on system
board
v Compatible with SVGA and VGA
v 8 MB SDRAM video memory
Size:
v Height: 4.37 cm (1.75 inches, 1U)
v Depth: 63.5 cm (25 inches)
v Width: 44 cm (17.32 inches)
v Maximum weight: 19.05 kg (42 lb)
depending on your configuration
Integrated functions:
v Dual 10BASE-T/100BASE-TX
Ethernet controllers on the system
board with Alert on LAN
™
2
support
v Serial port
v Two USB ports
v Keyboard port
v Mouse port
v Dual-channel bus mastering IDE
controller
Hard disk controller:
v All models-Dual-channel bus
mastering IDE controller
v Some models-SCSI adapter
(Adaptec Ultra160) is installed in
one of the expansion-slots
Acoustical noise emissions:
v Sound power, idling: 6.6 bel
maximum
v Sound power, operating: 6.8 bel
maximum
Environment:
v Air temperature:
– Server on: 10° to 35° C (50.0° to
95.0° F). Altitude: 0 to 914 m
(2998.7 ft)
– Server on: 10° to 32° C (50.0° to
89.6° F). Altitude: 914 m (2998.7
ft) to 2133 m (6998.0 ft.)
– Server off: -40° to 60° C
(-104° to 140° F). Maximum
altitude: 2133 m (6998.0 ft)
v Humidity:
– Server on: 8% to 80%
– Server off: 5% to 100%
Heat output:
Approximate heat output in British
thermal unit (Btu) per hour
v Minimum configuration: 171 Btu (50
watts)
v Maximum configuration: 410 Btu
(120 watts)
Electrical input:
v Sine-wave input (47-63 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.213 kVA
*KB equals approximately 1000 bytes. MB equals approximately 1000000 bytes. GB
equals approximately 1000000000 bytes.
4 Hardware Maintenance Manual: xSeries 300
What the IBM xSeries 300 offers
The design of your server takes advantage of advancements in memory
management and data storage. Your server includes:
v Impressive performance using the latest microprocessor technology.
Your server comes with one Intel Celeron or one Pentium III microprocessor
installed.
v Large system memory
The memory bus in your 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 inline memory
modules (DIMMs).
v Systems-management capabilities
See the documentation provided with your systems-management software for
more information.
v Integrated network environment support
Your server comes with two Intel Ethernet controllers on the system board.
These Ethernet controllers have 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 your server provide programs to
help you set up your 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 your server.
Chapter 2. General information 5
Reliability, availability, and serviceability features
Three of the most important features in server design are reliability, availability,
and serviceability (RAS). These RAS features help to ensure the integrity of the
data stored on your server; that your 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 your server supports.
v Reliability features
– Boot block recovery
– Cooling fans with speed-sensing capability
– Customer-upgradable basic input and output system (BIOS) code
– ECC front-side buses (FSBs) and L2 cache
– Advanced configuration and power interface (ACPI)
– Power-on self-test (POST)
– SDRAM with serial presence detect (SPD)
v Availability features
– 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 setup programs
– Failover Ethernet support
– Menu-driven diagnostic programs on CD-ROM
– Microsoft
– Monitoring support for temperature, voltage, and fan speed
– Server management
– Wake on LAN
v Serviceability features
– 24 hours per day, seven days a week customer support
– Adaptec 29160LP built-in self-test (BIST)
– Alert on LAN 2
– CD-ROM-based diagnostics
– Diagnostic support of Ethernet controllers
– Error codes and messages
– Processor serial number access
– Read-only memory (ROM) checksums
– Standard cables present detection
– Standby voltage for system management features and monitoring
– System error logging
– Vital product data (VPD) (includes information stored in nonvolatile memory
for easier remote viewing)
®
Windows NT®failover support
®
capability
™
2
2. Service availability will vary by country. Response time will vary depending on the number and nature of incoming calls.
6 Hardware Maintenance Manual: xSeries 300
Server controls and indicators
The following section identifies the controls and indicators on the front and rear of
your server.
Front view
Power control
button
Power-on
light (green)
Reset
button
System error
light (amber)
Diskette drive
activity light
(green)
Diskette eject
button
light (green)
CD eject buttonCD activity
Power-control button: Press this button to manually turn the server on or off.
Power-on light: This green LED lights and stays on when you turn on your server,
and it blinks when the server is in standby mode.
Reset button: Press this button to reset the server and run the power-on self-test
(POST). You might need to use a pen or the end of a straightened paper clip to
press the button.
System-error light: This amber LED lights when a system error occurs.
Diskette drive activity light: When this LED is on, it indicates that the diskette
drive is in use.
Diskette-eject button: Push this button to release a diskette from the drive.
CD eject button: Push this button to release a CD from the drive.
CD drive activity light: When this light is on, it indicates that the CD-ROM drive
is in use.
Chapter 2. General information 7
Rear view
System power
connector
Ethernet 1 link
indicator (amber)
Ethernet 1 speed
indicator (green)
Mouse or auxilary
pointing device connector
Keyboard port
Power-on light (green)
Video port
Ethernet 2 link
indicator (amber)
Ethernet 2 speed
indicator (green)
System error
light (amber)
USB 2
USB 1
Serial port
System power connector: The system power cord connects here to provide power
to the system.
Ethernet 1 link indicator: This amber LED lights when there is an active link
connection on the 10BASE-T or 100BASE-TX interface for Ethernet port 1.
Ethernet 1 speed indicator: This green LED lights when the speed of the Ethernet
LAN that is connected to Ethernet port 1 is 100 Mbps.
Auxiliary pointing device: Signal cables for a mouse, trackball, or other pointing
device connect to the Auxiliary pointing device connector.
Keyboard port: Signal cables for a keyboard connect to the keyboard port.
Power-on light: This green LED lights and stays on when you turn on your server
and will blink when the server is in standby mode. This light duplicates the power
on light on the front of the server.
Video port: The signal cable for a monitor connects to the video port.
Serial port: Signal cables for modems or other serial devices connect to the serial
port.
USB 2: This is an automatically configured port that you can use to connect one or
more USB devices to the server, using Plug and Play technology.
USB 1: This is an automatically configured port that you can use to connect one or
more USB devices to the server, using Plug and Play technology.
System-error light: This amber LED lights when a system error occurs. This light
duplicates the system error light on the front of the server.
Ethernet 2 speed indicator: This green LED lights when the speed of the Ethernet
LAN connected to Ethernet port 2 is 100 Mbps.
Ethernet 2 link indicator: This amber LED lights when there is an active link
connection on the 10BASE-T or 100BASE-TX interface for Ethernet port 2.
8 Hardware Maintenance Manual: xSeries 300
Turning on the server
Turning on the server refers to the act of plugging the power cord of your server
into the power source and starting the operating system.
Complete the following steps to turn on the server:
1. Plug the power cord of your server into the power source.
Note: Plugging the power cord into a power source may cause the server to
start automatically. This is an acceptable action.
2. Wait 30 seconds, and then press the power control button on the front of the
server.
Turning off the server
Turning off the server refers to the act of disconnecting the server from the power
source.
Complete the following steps to turn off the server:
1. Refer to your operating system documentation for the proper procedure to shut
down the operating system.
Statement 5:
CAUTION:
The power control button on the device and the power switch on the power
supply do not turn off the electrical current supplied to the device. The
device also might have more than one power cord. To remove all electrical
current from the device, ensure that all power cords are disconnected from
the power source.
2
1
2. Press the power control button on the front of the server. This will put the
server in standby mode.
3. Disconnect the server from the power source.
Note: After you turn off the server, wait at least 5 seconds before you turn on
the server again.
Chapter 2. General information 9
Standby mode
Standby mode puts the server into a wait state. When in a wait state, the server is
not running the operating system, and all core logic is shut down.
Complete the following steps to put the server into the standby mode:
1. Refer to your operating system documentation for the proper procedure to
shutdown the operating system.
2. Press the power control button on the front of the server.
10 Hardware Maintenance Manual: xSeries 300
Chapter 3. Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with the server.
If you cannot locate and correct the problem using the information in this section,
refer to Chapter 7, “Symptom-to-FRU index” on page 63 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 12 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 63“.
POST error messages
The possible types of beep codes that your system might emit are:
© Copyright IBM Corp. 2000 11
Repeating long beeps
Indicates that a memory error has occurred. Ensure that all DIMMs are
correctly installed.
One long beep and two short beeps
Indicates that a video error has occurred and the BIOS cannot initialize the
video screen to display any additional information. Ensure that the video
adapter is correctly installed.
For a list of POST errors, see “POST error codes” on page 69.
Small computer system interface messages (some models)
The following table lists actions to take if you receive a SCSI error message.
Note: If the server does not have a hard disk drive, ignore any message that
indicates that the BIOS is not installed.
You will get these messages only when running the SCSI Select Utility.
Table 1. 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.
12 Hardware Maintenance Manual: xSeries 300
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
Aborted
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.
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.
Chapter 3. Diagnostics 13
Test Specific String
This is additional information that is used to analyze the problem.
Starting the diagnostic programs
The IBM Enhanced Diagnostics programs will isolate your server hardware from
software that you have installed on your hard disk drive. The programs run
independently of the operating system, and must be run either from the CD or
diskette. This method of testing is generally used when other methods are not
accessible or have not been successful in isolating a problem suspected to be
hardware related.
An IBM Enhanced Diagnostics CD comes with the server. You can also download
the latest image of the diagnostics from the World Wide Web at
http://www.ibm.com/pc/support.
Note: When using diagnostics with a USB Keyboard and Mouse attached, go into
Setup and enable USB emulation.
1. Press F1 Config/Setup
2. Select Devices and I/O Ports
3. Select USB Setup
4. Make sure USB Keyboard and Mouse are enabled.
Using the diagnostics CD
To start the IBM Enhanced Diagnostics using the CD, do the following:
1. Turn off your server and any peripheral devices.
2. Turn on all attached devices; then, turn your server on.
3. When you see Press F1 For Configuration/Setup, press the F1 key.
4. When the Configuration/Setup Utility menu appears, select Start Options.
5. From the Start Options menu, select Startup Sequence.
6. Note the device selected as the First Startup Device. Later, you must restore
this setting.
7. Select CD-ROM as the First Startup Device.
8. Press Esc two times to return to the Configuration/Setup Utility menu.
9. Place the IBM Enhanced Diagnostics CD in the CD-ROM drive.
10. Select Save & Exit Setup and follow the prompts. The diagnostics will load.
Follow the instructions on the screen to run the diagnostics.
Important
When you finish running the diagnostics and utilities, remove the CD from the CD-ROM
drive and turn off the server. You must restore the First Startup Device to the original
setting. Use steps 2 through 8 of this procedure to do this.
Downloading the diagnostics program
Do the following to download the latest image of the IBM Enhanced Diagnostics
from the World Wide Web and create a startable Enhanced Diagnostics diskette:
1. Go to the following World Wide Web site: http://www.ibm.com/pc/support/
2. Download the diagnostics file for your server to a hard disk drive directory
(not to a diskette).
3. Go to a DOS prompt and change to the directory where the file was
downloaded.
14 Hardware Maintenance Manual: xSeries 300
4. Insert a blank high-density diskette in diskette drive A.
5. Type in the following, and then press Enter: filename a: where filename is the
name of the file you downloaded from the Web.
The downloaded file is self-extracting and will be copied to the diskette. When the
copy completes, you have a startable IBM Enhanced Diagnostics diskette.
Using the diagnostic diskette
Do the following to start the IBM Enhanced Diagnostics using the diagnostics
diskette, do the following:
1. Turn off your server and any peripheral devices.
2. Insert the IBM Enhanced Diagnostics diskette into the diskette drive.
3. Turn on all attached devices; then, turn on the server.
4. Follow the instructions on the screen.
5. Place the IBM Enhanced Diagnostics CD in the CD-ROM drive. The diagnostics
will load. Follow the instructions on the screen to run the diagnostics.
When the tests have completed, you can view the Test Log by selecting Utility
from the top of the screen.
If the hardware checks out OK but the problem persists during normal server
operations, a software error might be the cause. If you suspect a software problem,
refer to the information that comes with the software package.
Viewing the test log
The test log records data about system failures and other pertinent information.
The test log will not contain any information until after the diagnostic program has
run.
Note: If you already are running the diagnostic programs, begin with step 4
1. Insert the IBM Enhanced Diagnostics CD.
2. Turn on the system and watch the screen.
If the system is on, shut down your operating system and restart the system.
3. If a power-on password is set, the system prompts you for it. Type in the
appropriate password; then, press Enter.
4. Run the appropriate diagnostics program and when the Diagnostic Programs
screen appears, select Utility.
5. Select View Test Log from the list that appears; then, follow the instructions on
the screen.
6. 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.
When you turn off the power to the server, the test log is cleared.
Diagnostic error message tables
For descriptions of the error messages that might appear when you run the
diagnostic programs, see “Diagnostic error codes” on page 63. If diagnostic error
messages appear that are not listed in those tables, make sure that the server has
the latest levels of BIOS, Advanced System Management Processor, ServeRAID,
and diagnostics microcode installed.
Chapter 3. Diagnostics 15
Power checkout
Power problems can be difficult to troubleshoot. For instance, a short circuit can
exist anywhere on any of the power distribution busses. Usually a short circuit will
cause the power subsystem to shut down because of an overcurrent condition.
A general procedure for troubleshooting power problems is as follows:
1. Power off the server and disconnect the AC cord(s).
2. Check for loose cables in the power subsystem. Also check for short circuits, for
instance if there is a loose screw causing a short circuit on a circuit board.
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 70).
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 70).
16 Hardware Maintenance Manual: xSeries 300
Recovering BIOS code
If the BIOS code has become damaged, such as from a power failure during a flash
update, you can recover the BIOS using the boot block jumper and a BIOS flash
diskette. The boot block jumper selects between normal BIOS mode and flash
recovery mode. In the normal position, the jumper will be installed on pins 2 and
3. In the recovery position, the jumper will be installed on pins 1 and 2.
There are two choices when flashing BIOS. If you select flashing to Server mode,
internal only COM PORT 2 and USB keyboard and mouse emulation will be OFF
by default. These can be turned on, either individually or both, by going into F1
setup and turning them on. This will require a reboot. If you select flashing to
Appliance mode, internal only COM PORT 2 and USB keyboard and mouse
emulation will be ON by default. They can be turned off, either individually or
both, by going into F1 setup and turning them off. This will require a reboot.
If the only US devices attached are keyboard and mouse and they are not working,
investigate the F1 setup settings for these options. You can use a USB keyboard to
press F1 and get into setup.
Note: 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 to make a BIOS flash diskette from the World Wide Web.
Go to http://www.ibm.com/pc/support/, select IBM System Support,
and then make the selections for your system.
Complete the following steps to recover the BIOS code:
1. Turn off the server and peripheral devices and disconnect all external cables
and power cords; then, remove the cover, see “Removing the cover” on
page 38.
Chapter 3. Diagnostics 17
2. Locate jumper JROM1 on the system board.
3. Move the JROM1 jumper to the alternate position (pins 1 and 2) to enable the
BIOS recovery mode.
4. Reinstall the cover, see “Installing the cover” on page 53.
5. Reconnect all external cables and power cords and turn on the peripheral
devices.
6. Insert the BIOS flash diskette in the diskette drive.
7. Restart the server. The BIOS begins the power-on self-test.
8. The BIOS flash utility automatically starts.
9. When prompted as to whether you want to save the current code to a
diskette, type N.
10. When prompted, type Y to continue the flash process.
11. The system automatically starts the flash utility a second time.
12. When prompted as to whether you want to save the current BIOS code, stop
the process by removing the BIOS flash diskette from the diskette drive.
13. Turn off the server and peripheral devices and disconnect all external cables
and power cords; then, remove the cover, see “Removing the cover” on
page 38.
14. Move the JROM1 jumper to the normal position (pins 2 and 3) to return to
normal startup mode.
15. Reinstall the cover, see “Installing the cover” on page 53.
16. Reconnect all external cables and power cords and turn on the peripheral
devices.
18 Hardware Maintenance Manual: xSeries 300
Clearing CMOS
17. Restart the server, which should start up normally.
If you need to erase configuration information, you must move the CMOS jumper.
See the illustration in “Recovering BIOS code” on page 17 for the location of the
CMOS jumper.
The default position is a jumper installed on pins 1 and 2. Before you change the
position of this jumper, you must turn off the server and peripheral devices, and
disconnect all external cables and power cords. Remove the cover and then move
the jumper to pins 2 and 3.
After moving the jumper, wait at least 5 minutes for the CMOS information to
clear.
Changing the position of this jumper erases all configuration and setup
information, including the power-on and administrator passwords. Therefore, you
must reconfigure the server after clearing CMOS memory (see Chapter 4,
“Configuring the server” on page 29). If possible, record your server configuration
information before moving the CMOS jumper.
After you clear the CMOS information, move the jumper back to its normal
position (pins 1 and 2). Reconnect the external cables and power cords; then, turn
on the peripheral devices and the server.
Replacing the battery
When replacing the battery, you must replace it with a lithium battery of the same
type from the same manufacturer. To avoid possible danger, read and follow the
safety statement below.
To order replacement batteries, call 1-800-772-2227 within the United States, and
1-800-465-7999 or 1-800-465-6666 within Canada. Outside the U.S. and Canada, call
your IBM reseller or IBM marketing representative.
Note: After you replace the battery, you must reconfigure your system and reset
the system date and time.
Chapter 3. Diagnostics 19
CAUTION:
When replacing the battery, use only IBM Part Number 33F8354 or an equivalent
type battery recommended by the manufacturer. If your 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 36, 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 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.
d. Ensure that the battery clip is touching the base of the battery socket by
pressing gently on the clip.
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.
20 Hardware Maintenance Manual: xSeries 300
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 your server.
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
Attention:
If using AOL/2 or system supported monitoring software, and you are receiving a
thermal alert with no fan alert, check SYSFA1 and CPUFA2, which are
unmonitored and therefore cannot generate alerts, to make certain that those fans
are connected to planar power and are functional.
If the system powers itself down, the cause maybe an overheated processor
causing a thermal trip. One of your checks should be to ensure that both system
fans and both CPU fans are connected to planar power and are functional.
In addition, ensure that the environmental specifications for the server are met. See
“Features and specifications” on page 4.
Note: The speed of the fans will increase if:
Diagnosing errors
To find solutions to problems that have definite symptoms, see “Error symptoms”
on page 66.
If you cannot find the problem there, go to “Starting the diagnostic programs” on
page 14 to test the server.
v One fan fails.
v Ambient temperature gets too high.
Chapter 3. Diagnostics 21
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.
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 your
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.
22 Hardware Maintenance Manual: xSeries 300
Loading...