IBM xSeries 230 6RY, xSeries 230 61Y Hardware Maintenance Manual
Hardware Maintenance Manual
xSeries 230 Models 6RY, 61Y
Hardware Maintenance Manual
xSeries 230 Models 6RY, 61Y
to
©
US
Note: 1Before using this information and the product it supports, be sure to read the general information under “Notices” on
page 183.
Third Edition (March 2004)
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
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.
Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Be
©
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
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 230.
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
iv
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.
Online Support
IBM Online Addresses
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a
cabo cualquier operación.
Use the World Wide We b (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
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
©
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 . . . . . . . . . .3
What your IBM xSeries 230 offers . . . . . . .5
Reliability, availability, and serviceability features . .6
Server controls and indicators . . . . . . . .7
Starting the server . . . . . . . . . . .9
Operator Information panel . . . . . . . . .10
Diagnostics . . . . . . . . . . . . .13
Diagnostic tools overview . . . . . . . . .13
POST . . . . . . . . . . . . . . . .13
Event/error logs . . . . . . . . . . . .13
Small computer system interface messages . . . .14
Identifying problems using status LEDs . . . . .14
Light path diagnostics . . . . . . . . . .14
Diagnostic programs and error messages . . . .15
Text messages . . . . . . . . . . . .16
Starting the diagnostic programs . . . . . .16
Viewing the test log . . . . . . . . . .17
Diagnostic error message tables . . . . . . .17
Recovering BIOS . . . . . . . . . . . .18
Troubleshooting the Ethernet controller . . . . .18
Network connection problems . . . . . . .18
Ethernet controller troubleshooting chart . . .19
Ethernet controller messages . . . . . . . . .20
Novell NetWare or IntraNetWare server ODI
driver messages . . . . . . . . . . . .20
Network driver interface specification 2.01
(OS/2) driver messages . . . . . . . . .22
NDIS 4.0 (Windows NT) driver messages . . .24
UNIX messages . . . . . . . . . . . .24
Power checkout . . . . . . . . . . . . .26
Replacing the battery . . . . . . . . . . .27
Temperature checkout . . . . . . . . . . .28
Configuring the server . . . . . . . .31
Using the Configuration/Setup Utility program . .31
Starting the Configuration/Setup Utility program 31
Choices available from the Configuration/Setup
main menu . . . . . . . . . . . . .31
Using passwords . . . . . . . . . . .35
Bypassing an unknown power-on password . . .37
Using the SCSISelect utility program . . . . . .37
Starting the SCSISelect utility program . . . .37
Choices available from the SCSISelect menu . .38
Installing options . . . . . . . . . .41
Exploded view of the xSeries 230 server . . . . .41
System board layout . . . . . . . . . . .41
System board options connectors . . . . . .42
System board internal cable connectors . . . .43
System board external port connectors . . . .43
System board switches and jumpers . . . . .44
System board LED locations . . . . . . . .45
Before you begin . . . . . . . . . . . .47
System reliability considerations . . . . . .47
Working inside a server with power on . . . .47
Handling static sensitive devices . . . . . .48
Removing the cover, door, and bezel . . . . . .48
Removing the left-side cover (tower model) . .49
Removing the cover (rack model) . . . . . .49
Removing the server door (tower model) . . .50
Removing the bezel (rack or tower) . . . . .51
Working with adapters . . . . . . . . . .51
Adapter considerations . . . . . . . . .52
Installing an adapter . . . . . . . . . .53
Installing internal drives . . . . . . . . . .54
Internal drive bays . . . . . . . . . . .54
Hot-swap drives . . . . . . . . . . . .56
Non-hot-swap drives . . . . . . . . . .56
Preinstallation steps (all bays) . . . . . . .57
Installing a hot-swap drive . . . . . . . .57
Installing a non-hot-swap drive . . . . . . .60
Installing memory modules . . . . . . . . .61
Installing a microprocessor . . . . . . . . .63
Installing or removing a power supply . . . . .65
Adding a power supply . . . . . . . . .66
Removing a hot-swap power supply . . . . .67
Removing the only power supply . . . . . .68
Replacing a fan assembly . . . . . . . . . .69
Installing the cover . . . . . . . . . . . .70
Installing the cover (tower) . . . . . . . .70
Installing the cover (rack) . . . . . . . . .71
Connecting external options . . . . . . . . .72
Installation procedure . . . . . . . . . .72
I/O connector locations . . . . . . . . . .73
Input/Output ports . . . . . . . . . . .73
Parallel port . . . . . . . . . . . . .74
Serial ports . . . . . . . . . . . . .75
Universal Serial Bus ports . . . . . . . .76
Keyboard port . . . . . . . . . . . .77
Auxiliary-device (pointing device) port . . . .77
Video port . . . . . . . . . . . . . .78
SCSI ports . . . . . . . . . . . . . .78
Ethernet port . . . . . . . . . . . . .80
Advanced System Management ports . . . . .84
Cabling the server . . . . . . . . . . . .85
Netfinity Manager . . . . . . . . . .87
Managing your IBM Netfinity server with Netfinity
Manager . . . . . . . . . . . . . . .87
Netfinity Manager documentation . . . . . . .88
Copyright IBM Corp. 2000
v
98
No
vi
Netfinity Manager system requirements . . . . .88
Netfinity Manager for OS/2 system requirements 88
Netfinity Manager for Windows 95 and Windows
system requirements . . . . . . . . .89
Netfinity Manager for Windows NT system
requirements . . . . . . . . . . . . .89
Starting the Netfinity Manager installation program 90
Netfinity Manager database support . . . . . .96
DB2 database support . . . . . . . . . .97
Lotus Notes database support . . . . . . . 101
ODBC database support . . . . . . . . . 102
Starting Netfinity Manager . . . . . . . . . 106
Netfinity Manager Service Manager . . . . . 107
Netfinity Manager service descriptions . . . . 108
Delaying Netfinity Manager startup on OS/2
systems . . . . . . . . . . . . . .112
Getting more information about Netfinity Manager 113
Installation options . . . . . . . . . . .114
Automated installation . . . . . . . . .114
Customized installation . . . . . . . . .115
FRU information (service only) . . . .119
Removing the external LED card . . . . . . .119
Removing the power reset card . . . . . . . 120
Removing the rear cable bracket . . . . . . . 121
Removing the DASD backplane assembly . . . . 122
Removing the power supply backplane . . . . . 122
Removing the system board . . . . . . . . 123
Symptom-to-FRU index . . . . . . . 125
Beep Symptoms . . . . . . . . . . . . 125
Beep symptoms . . . . . . . . . . . 127
Information panel system error LED . . . . . . 128
Diagnostic error codes . . . . . . . . . . 129
Error symptoms . . . . . . . . . . . . 132
Power supply LED errors . . . . . . . . . 133
POST error codes . . . . . . . . . . . . 134
SCSI error codes . . . . . . . . . . . . 140
Temperature error messages . . . . . . . . 140
Fan error messages . . . . . . . . . . . 141
Power error messages . . . . . . . . . . 141
System shutdown . . . . . . . . . . . . 142
Voltage related system shutdown . . . . . . 142
Temperature related system shutdown . . . . 142
DASD checkout . . . . . . . . . . . . 143
Host Built-In Self Test (BIST) . . . . . . . . 143
Bus fault messages . . . . . . . . . . . 143
Undetermined Problems . . . . . . . . . . 143
Parts listing (xSeries 230) . . . . . . 145
Keyboards . . . . . . . . . . . . . . 147
Power cords . . . . . . . . . . . . . . 147
Related service information . . . . . 149
Safety information . . . . . . . . . . . . 149
General safety . . . . . . . . . . . . 149
Electrical safety . . . . . . . . . . . . 150
Safety inspection guide . . . . . . . . . 151
Handling electrostatic discharge-sensitive
devices . . . . . . . . . . . . . . 152
Grounding requirements . . . . . . . . 153
Safety notices (multi-lingual translations) . . . 153
Send us your comments! . . . . . . . . . 182
Problem determination tips . . . . . . . . . 182
Notices . . . . . . . . . . . . . . . 183
Trademarks . . . . . . . . . . . . . . 183
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
on
A
A
v
v
v
If
1.
2. If
3. If
4. If
5.
6.
7.
1. IS
©
General checkout
The server diagnostic programs are stored in upgradable read-only memory (ROM)
the system board. These programs are the primary method of testing the major
components of the server: the system board, Ethernet controller, video controller,
RAM, keyboard, mouse (pointing device), diskette drive, serial ports, hard drives,
and parallel port. Yo u can also use them to test some external devices. See
“Diagnostic tools overview” on page 13.
Also, if you cannot determine whether a problem is caused by the hardware or by
the software, you can run the diagnostic programs to confirm that the hardware is
working properly.
When you run the diagnostic programs, a single problem might cause several error
messages. When this occurs, work to correct the cause of the first error message.
After the cause of the first error message is corrected, the other error messages
might not occur the next time you run the test.
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.
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 systems are located near the failing system.
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:
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.
multiple error codes are displayed, diagnose the first error code displayed.
the computer hangs with a POST error, go to the “POST error codes” on
page 134.
the computer hangs and no error is displayed, go to “Undetermined
Problems” on page 143.
Power supply problems, see “Power supply LED errors” on page 133.
Safety information, see “Safety information” on page 149.
For intermittent problems, check the error log; see “POST error codes” on page
134.
THE SYSTEM PART OF A CLUSTER?
YES.Schedule maintenance with the customer. Shut down all systems related to the
cluster. Run storage test.
NO. Go to step 2.
Copyright IBM Corp. 2000
1
IS
v
v
v
v
v
v
v
v
v
v
a.
b.
If
If
2
2.
THE SYSTEM 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 134.
Check the information LED panel System Error LED; if on, see “Information
panel system error LED” on page 128.
Check the System Error Log. If an error was recorded by the system, see
“Symptom-to-FRU index” on page 125.
Start the Diagnostic Programs. See “Starting the diagnostic programs” on
page 16.
Check for the following responses:
One beep.
Readable instructions or the Main Menu.
DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
3.
NO.Find the failure symptom in “Symptom-to-FRU index” on page 125.
Run the Diagnostic Programs. If necessary, refer to “Starting the diagnostic
YES.
programs” on page 16.
you receive an error, go to “Symptom-to-FRU index” on page 125.
the diagnostics completed successfully and you still suspect a problem, see
“Undetermined Problems” on page 143.
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
To
v
v
v
v
v
v
v
v
v
v
v
v
v
©
General information
Your IBM
®
(SMP) server. It is ideally suited for networking environments that require superior
microprocessor performance, efficient memory management, flexibility, and large
amounts of reliable data storage.
Your xSeries 230 comes with a three-year limited warranty and IBM PC Server
90-Day Start Up Support. If you have access to the World Wide Web, you can
obtain up-to-date information about your xSeries 230 model and other IBM server
products at the following World Wide We b address:
http://www.ibm.com/pc/support
Your server serial number and model number are located on labels on the rear of
the server and on the front under the trim bezel. Yo u will need these numbers
when you register your server with IBM. To register your server, go to the
following World Wide We b address:
http://www.ibm.com/pc/register
find the meanings of various computer-related terms, you can access the IBM
xSeries 230 at the following World Wide We b address:
http://www.networking.ibm.com/nsg/nsgmain.htm
Features and specifications
The following table provides a summary of the features and specifications for your
xSeries 230 server.
xSeries 230 is a high-performance, symmetric multiprocessing
Microprocessor:
®
Intel
Pentium III microprocessor with MMX technology and SIMD extensions
256 KB Level-2 cache (min.)
Supports up to two microprocessors
Memory:
Standard: 128 MB
Maximum: 4GB
Type: 133 MHz, ECC, SDRAM, Registered DIMMs
Sockets: 4 dual inline sockets
Drives
standard:
Diskette: 1.44 MB
CD-ROM: 40X IDE
Expansion
bays:
Hot-swap: 6 slim high or 3 half high
Non-hot-swap: Three 5.25-inch (one used by CD-ROM drive)
expansion slots:
PCI
Three 33 MHz/ 64-bit slots
Two 33 MHz/ 32-bit slots
Power
supplies: 250 W (115-230 Vac)
Copyright IBM Corp. 2000
3
v
v S3
v
v 4 MB
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
–
–
m
–
–
–
v
v
v
4
v
Standard: One, non-hot-swappable
Maximum: Three, only with optional power backplane that enables multiple
power supplies and hot-swappability
Video:
Savage 4 video controller (integrated on system board)
Compatible with SVGA and VGA
video memory
(Rack Model)
Size
Height: 220 mm (8.7 in.)
Depth: 630 mm (24.8 in.)
Width: 440 mm (17.3 in.)
Weight: approximately 27.22 Kg (60 lb.) when fully configured
(Tower Model)
Size
Height: 440 mm (17.3 in.)
Depth: 660 mm (26.0 in.)
Width: 220 mm (8.7 in.)
Weight: approximately 27.22 Kg (60 lb.) when fully configured
Integrated
functions:
Netfinity Advanced System Management processor
Dual channel Ultra2 SCSI controller (both channels internal)
One 10BASE-T/!00BASE-TX AMD Ethernet controller
One S3 Savage 4 video controller
Two serial ports
One parallel port
Two Universal Serial Bus (USB) ports
Keyboard port
Mouse port
Video port
Acoustical
noise emissions:
Sound power, idling: 6.0 bel maximum
Sound power, operating: 6.0 bel maximum
Sound pressure, operating: 45 dBa 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
(6998.0 ft.)
Server off: 10║ to 43║ C (50.0║ to 109.4║ F). Maximum altitude: 2133 m (6998.0
ft.)
v
Humidity:
Server on: 8% to 80%
Server off: 8% to 80%
Heat output: Approximate heat output in British Thermal Units (BTU) per hour:
Minimum configuration: 683 BTU (200 watts)
Maximum configuration: 2048 BTU (600 watts)
Electrical
Sine-wave input (50-60 Hz) required
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
input:
–
–
–
–
–
v
to
v
v
If
to
v
v
v
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
Input kilovolt-amperes (kVA) approximately: Minimum: 0.08 kVA
v
Maximum: 0.42 kVA
What your IBM xSeries 230 offers
The unique design of your server takes advantage of advancements in symmetric
multiprocessing (SMP), data storage, Your server combines:
Impressive performance using an innovative approach to SMP
Your server supports up to two Pentium III microprocessors. Your server comes
with one microprocessor installed; you can install an additional microprocessor
enhance performance and provide SMP capability.
Large data-storage and hot-swap capabilities
All models of the server support up to six hot-swap hard disk drives. This
hot-swap feature enables you to remove and replace hard disk drives without
turning off the server.
Redundant power capabilities
The standard 250-watt power supply in your server can handle a load of up to
250 watts. By replacing the power backplane with the optional backplane that
provides hot-swap capability to the power supplies, you can install a second,
optional power supply. This provides a full 500 watts of power. If the average
load on your server is less than 250 watts and a problem occurs with one of the
power supplies, the other power supply can handle the load (redundant power).
the average load on your server is greater than 250 watts, and you have
installed a second power supply, you can install a third, optional power supply
provide redundancy.
The OVERCURRENT light emitting diode (LED) on the system board is lit when
the power load is 250 watts or greater with two power supplies, or when the
power load is 500 watts or greater with three power supplies.
Large system memory
The memory bus in your server supports up to 4 GB of system 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-random access memory (SDRAM) DIMMs (Intel PC-Registered SDIMM
Specifications, Revision 1.0 or later), synchronous, dual inline memory modules.
System-management capabilities
Your server comes with a Netfinity Advanced System Management Processor on
the system board. This processor, in conjunction with the Netfinity Manager
provided on your ServerGuide CDs, allows you to manage the functions of the
server locally and remotely. The Netfinity Advanced System Management
Processor also provides system monitoring, event recording, and dial-out alert
capability.
™
Note: The Netfinity Advanced System Management Processor is sometimes
Refer to the Advanced System Management section for more information.
Integrated network environment support
referred to as the service processor.
General information
5
v
v
As
v
v
v
v
v
v
v
v
v
v
v
v
v
6
Your 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.
The controller provides full-duplex (FDX) capability, which allows simultaneous
transmission and reception of data on the Ethernet local area network (LAN).
Redundant network-interface card
The addition of an optional, redundant network interface card (NIC) provides a
failover capability to a redundant Ethernet connection. If a problem occurs with
the primary Ethernet connection, all Ethernet traffic associated with this primary
connection is automatically switched to the redundant NIC. This switching
occurs without data loss and without user intervention.
IBM ServerGuide CDs
The ServerGuide CDs included with IBM xSeries servers provide programs to
help you set up your server and install the network operating system (NOS).
The ServerGuide program detects the hardware options installed, and provides
the correct configuration program and device drivers. In addition, the
ServerGuide CDs include a variety of application programs such as IBM Update
Connector to help keep your server BIOS and microcode updated, and IBM
Netfinity Manager for systems management.
For more information about the ServerGuide CDs, see the ServerGuide and
Netfinity Manager Information section.
server is designed to be cost-effective, powerful, and flexible. It uses
Your
peripheral component interconnect (PCI) bus architecture to provide compatibility
with a wide range of existing hardware devices and software applications.
always, your IBM server meets stringent worldwide certifications for power,
electromagnetic compatibility (EMC), and safety. Refer to the ‘Safety Information’
section. for additional information.
Reliability, availability, and serviceability features
Three of the most important features in server design are reliability, availability,
and serviceability (RAS). These factors 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.
Many of these features are explained in later chapters or sections.
Menu-driven setup, system configuration, RAID configuration, and diagnostic
programs
Power-on self-test (POST)
Integrated Netfinity Advanced System Management Processor
Predictive failure alerts
System auto-configuring from configuration menu
Remote system problem-determination support
Power and temperature monitoring
Fault-resilient startup
Hot-swap hard drive bays
Error codes and messages
System error logging
Upgradable BIOS, diagnostics, and Netfinity Advanced System Management
Processor code
Automatic restart after a power failure
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
v
v
v
v
v
v
v
v
v
Parity checking on the SCSI and PCI buses
Error checking and correcting (ECC) memory
Redundant hot-swap power supply option
Redundant hot-swap cooling
Redundant Ethernet capabilities (with optional adapter)
Vital Product Data (VPD) on processor complex, system board, power backplane,
SCSI backplane, and each power supply.
Operator information panel
Diagnostic LEDs on the system board
Remote Connect
Server controls and indicators
1
2
3
4
5
6
7
8
Operator information panel
Hard disk drive activity light
Hard disk drive status light
Serial number
Cover release latch
Reset button
Power control button
Power control button shield (if installed)
General information
7
8
Rack model
1
2
3
4
5
6
7
8
Cover release latch
Serial number
Hard disk drive activity light
Hard disk drive status light
Reset button
Power control button
Power control button shield (if installed)
Operator information panel
Reset Button: Press this button to reset the server and run the power-on self-test
(POST).
Operator Information Panel: The lights on this panel give status information for
your server. See “Operator Information panel” on page 10 for more information.
Hard Disk Status Light: Each of the hot-swap drives has a Hard Disk Status light.
When this amber light is on continuously, the drive has failed. When the light
flashes slowly (one flash per second), the drive is being rebuilt. When the light
flashes rapidly (three flashes per second), the controller is identifying the drive.
Hard Disk Activity Light: Each of the hot-swap drives has a Hard Disk Activity
light. When this green light is flashing, the controller is accessing the drive.
Rear view
(tower shown)
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
AC
DC
AC
DC
v
v If
v
v
1
2
power LED
power LED
Power Light:This light provides status information about the power supply.
During normal operation, both the AC and DC Power lights are on. For any other
combination of lights, see “Power supply LEDs” on page 14.
Power Light:This light provides status information about the power supply.
During normal operation, both the AC and DC Power lights are on. For any other
combination of lights, see “Power supply LEDs” on page 14.
Starting the server
After you have plugged the power cord of your server into an electrical outlet and
the power supply has been turned on, the server can be activated in several ways:
Yo u can turn on the server by pressing the Power control button on the front of
the server.
Note: If you have just plugged the power cord of your server into an electrical
outlet, you will have to wait approximately 20 seconds before pressing the
Power control button.
the server is activated and a power failure occurs, the server will start
automatically when power is restored.
Pressing the Reset button resets the server and runs the power-on self-test.
The server can also be powered on by the Netfinity Advanced System
Management Processor.
Deactivating
The server can be deactivated as follows:
the server
General information
9
v
v
v
10
CAUTION:
The power control button on the device and/or 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
Yo u can turn off the server by pressing the Power control button on the front of
the server. Pressing the Power control button starts an orderly shutdown of the
operating system, if this feature is supported by your operating system, and
places the server in standby mode.
Note: After turning off the server, wait at least 5 seconds before pressing the
Power control button to power the server on again.
Yo u can press and hold the Power control button for more than 4 seconds to
cause an immediate shutdown of the server and place the server in standby
mode. This feature can be used if the operating system hangs.
Yo u can disconnect the server power cords from the electrical outlets to shut off
all power to the server.
Note: Wait about 15 seconds after disconnecting the power cords for your
system to stop running. Watch for the System Power light on the operator
information panel to stop blinking.
Operator Information panel
The operator information panel on the front of the server contains status lights.
1
2
3
4
5
Information light
System error light
Ethernet transmit/receive activity light
Ethernet link status light
Ethernet speed light
OK
100
MB
LINK
OK
TX
RX
6
7
8
Power-on light
POST complete light
SCSI hard disk drive in-use light
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
is
Power-on light
This green LED lights when system power is present in the server. When
this light flashes, the server is in standby mode (the system power supply
turned off and AC current is present). If this light is not on, the power
cord is not connected, the power supply has failed, or this LED has failed.
POST complete light
This green LED lights when the server completes the power-on self-test
(POST) without any errors.
SCSI Hard Disk Drive In-use Light:
This green LED lights when there is activity on a hard disk drive.
Information Light:
This amber LED lights when the information log contains information
about certain conditions in your server that might affect performance. For
example, the light will be on if your server does not have redundant
power. An LED on the diagnostic panel on the system board will also be
on.
System Error Light:
This amber LED lights when a system error occurs. An LED on the
diagnostic panel on the system board will also be on to further isolate the
error.
Ethernet speed Light:
This green LED lights when the Ethernet LAN speed is 100 Mbps.
Ethernet Link Status Light:
This green LED lights when there is an active connection on the Ethernet
port.
Ethernet Transmit/Receive Activity Light:
This green LED lights when there is transmit or receive activity to or from
the server.
General information
11
12
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
v
on
v
v
If
If
1. If
2. A
to
©
Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with your server.
Diagnostic tools overview
The following tools are available to help you identify and resolve hardware-related
problems:
POST beep codes, error messages, and error logs
The power-on self-test (POST) generates beep codes and messages to indicate
successful test completion or the detection of a problem. See “POST error codes”
page 134 for more information.
Light path diagnostics
Your server has light-emitting diodes (LEDs) to help you identify problems with
server components. These LEDs are part of the light-path diagnostics that are
built into your server. By following the path of lights, you can quickly identify
the type of system error that occurred. See “Light path diagnostics” on page 14
and the table in “Information panel system error LED” on page 128 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 your server. See “Diagnostic programs and error
messages” on page 15 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.
POST finishes without detecting any problems, a single beep sounds, the first
screen of your operating system or application program appears, and the System
POST Complete (OK) light is illuminated on the operator information panel.
POST detects a problem, more than one beep sounds and an error message
appears on your screen. See “Beep Symptoms” on page 125 and “POST error
codes” on page 134 for more information.
Notes:
you have a power-on password or administrator password set, you must
type the password and press Enter, when prompted, before POST will continue.
single problem might cause several error messages. When this occurs, work
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.
Event/error logs
The POST error log contains the three most recent error codes and messages that
the system generated during POST. The System Event/Error Log contains all error
Copyright IBM Corp. 2000
13
To
If
14
messages issued during POST and all system status messages from the Netfinity
Advanced System Management Processor.
view the contents of the error logs, start the Configuration/Setup Utility
program; then, select Event/Error Logs from the main menu.
Small computer system interface messages
The table in “SCSI error codes” on page 140 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.
Yo u will get these messages only when running the SCSISelect Utility.
Identifying problems using status LEDs
the System Error light in the operator information panel on the front of the
server is on, one or more LEDs inside the server or on the power supplies will be
on. Use the light path diagnostics to identify the type of error that occurred.
Light path diagnostics
Yo u can use the light path diagnostics built into your server to quickly identify the
type of system error that occurred. Your server is designed so that any LEDs that
are illuminated remain illuminated when the server shuts down as long as the AC
power source is good and the power supplies can supply +5V dc current to the
server. This feature helps you isolate the problem if an error causes the server to
shut down. See “Light path diagnostics table” on page 15.
Power supply LEDs
The AC and DC Power LEDs on the power supply provide status information
about the power supply. See “Power supply LED errors” on page 133.
Diagnostics panel
The following illustration shows the LEDs on the diagnostics panel on the system
board. See “Light path diagnostics table” on page 15 below for information on
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
on
be
is
is
identifying problems using these LEDs.
PS1
PS2
PS3
NON
OVER
NMI
TEMP
FAN
MEM
CPU
PCI A
PCI B
VRM
DASD1
DASD2
Light path diagnostics table
The System Error LED on the operator information panel is lit when certain system
errors occur. If the System Error LED on your server is lit, use the table in
“Information panel system error LED” on page 128 to help determine the cause of
the error and the action you should take.
Diagnostic programs and error messages
The server diagnostic programs are stored in upgradable read-only memory (ROM)
the system board. These programs are the primary method of testing the major
components of your server.
Diagnostic error messages indicate that a problem exists; they are not intended to
used to identify a failing part.
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
ttt
the three-digit function code that indicates the function being tested
when the error occurred. For example, function code 089 is for the
microprocessor.
the three-digit failure code that indicates the exact test failure that was
encountered.
Diagnostics
15
is
cc is
is
is
is
To
1.
is
2.
3.
4.
5.
16
iii
the three-digit device ID. .
date is the date that the diagnostic test was run and the error recorded.
the check digit that is used to verify the validity of the information.
text message
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
the name of the function being tested when the error occurred. This
corresponds to the function code (fff) given in the previous list.
Result can be one of the following:
Passed: This result occurs when the diagnostic test completes without any
errors.
Failed:This result occurs when the diagnostic test discovers an error.
User Aborted:This result occurs when you stop the diagnostic test before it
complete.
Not Applicable:This result occurs when you specify a diagnostic test for a
device that is not present.
Aborted: This result occurs when the test could not proceed because of the
system configuration.
Warning:This result occurs when a possible problem is reported during the
diagnostic test, such as when a device that is to be tested is not installed.
Test Specific String
This is additional information that you can use to analyze the problem.
Starting the diagnostic programs
Yo u can press F1 while running the diagnostic programs to obtain Help
information. Yo u also can press F1 from within a help screen to obtain online
documentation from which you can select different categories. To exit Help and
return to where you left off, press Esc.
start the diagnostic programs:
Turn on the server and watch the screen.
Note: To run the diagnostic programs, you must start the server with the
highest level password that is set. That is, if an administrator password
set, you must enter the administrator password, not the power-on
password, to run the diagnostic programs.
When the message F2 for Diagnostics appears, press F2.
Type in the appropriate password; then, press Enter.
Select either Extended or Basic from the top of the screen.
When the Diagnostic Programs screen appears, select the test you want to run
from the list that appears; then, follow the instructions on the screen.
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
a. If
b.
c. If
d.
e.
If
To
1.
If
2.
If a
3.
4.
Notes:
the server stops during testing and you cannot continue, restart the
server and try running the diagnostic programs again.
The keyboard and mouse (pointing device) tests assume that a keyboard
and mouse are attached to the server.
you run the diagnostic programs with either no mouse or a USB mouse
attached to your server, you will not be able to navigate between test
categories using the Next Cat and Prev Cat buttons. All other functions
provided by mouse-selectable buttons are also available using the function
keys.
Yo u can test the USB keyboard by using the regular keyboard test. The
regular mouse test can test a USB mouse. Also, you can run the USB hub
test only if there are no USB devices attached.
Yo u 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.
the tests have completed, you can view the Test Log by selecting Utility
When
from the top of the screen.
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
view the test log:
Turn on the server and watch the screen.
the server is on, shut down your operating system and restart the server.
When the message F2 for Diagnostics appears, press F2.
power-on password or administrator password is set, the server prompts
you for it. Type in the appropriate password; then, press Enter.
When the Diagnostic Programs screen appears, select Utility from the top of
the screen.
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 message tables
The tables in “Diagnostic error codes” on page 129 provide descriptions of the
error messages that might appear when you run the diagnostic programs.
Attention: If diagnostic error messages appear that are not listed in the tables,
make sure that your server has the latest levels of BIOS, Advanced System
Management Processor, and diagnostics microcode installed.
Diagnostics
17
If
v
v
To
1.
2.
3.
4.
5.
6.
7.
8.
9.
If
v
If
5
If
a
18
Recovering BIOS
update, you can recover your BIOS using the recovery boot block and a BIOS flash
diskette.
Note: Yo u can obtain a BIOS flash diskette from one of the following sources:
The
overwritten. The recovery boot block is a section of code in this protected area that
enables the server to start up and to read a flash diskette. The flash utility recovers
the system BIOS from the BIOS recovery files on the diskette.
your BIOS has become corrupted, such as from a power failure during a flash
Use the ServerGuide program to make a BIOS flash diskette.
Download a BIOS flash diskette from the World Wide Web. Go to
http://www.pc.ibm.com/support/, select IBM Server Support, and make
the selections for your server.
flash memory of your server contains a protected area that cannot be
recover the BIOS:
Turn off the server and peripheral devices and disconnect all external cables
and power cords; then, remove the cover.
Locate the boot block jumper (J37) on the system board.
Place a jumper on pins 1 and 2 to enable BIOS recovery mode.
Insert the BIOS flash diskette into the diskette drive.
Restart the server.
The Recovery Boot screen will appear. A progress report, Loading data from
diskette xx%, is displayed. When programming is underway, a further
progress report, Programming block n of 7 yy%, is displayed. When recovery is
complete, Recovery complete, remove the diskette and return boot block
switch to the off position before rebooting is displayed.
Remove the flash diskette from the diskette drive.
Turn the server off.
Remove the jumper on the boot-block jumper block or move pins 2 and 3 to
return to normal startup mode.
Restart the server. The system should start up normally.
Troubleshooting the Ethernet controller
This section provides troubleshooting information for problems that might occur
with the 10/100 Mbps Ethernet controller.
Network connection problems
the Ethernet controller cannot connect to the network, check the following:
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.
you set the Ethernet controller to operate at 100 Mbps, you must use Category
cabling.
you directly connect two workstations (without a hub), or if you are not using
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.
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
v
–
–
–
v
v
v
v
v
v
v
v
v
v
v If
v If
v
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.
Check the Ethernet controller lights on the operator information panel.
These lights indicate whether a problem exists with the connector, cable, or hub.
The Ethernet Link Status light illuminates when the Ethernet controller
receives a LINK pulse from the hub. If the light is off, there might be a bad
connector or cable, or a problem with the hub.
The Ethernet Transmit/Receive Activity light illuminates when the Ethernet
controller sends or receives data over the Ethernet Network. If the Ethernet
Transmit/Receive Activity light is off, make sure that the hub and network
are operating and that the correct device drivers are loaded.
The Ethernet Speed 100 Mbps light illuminates when the Ethernet controller
LAN speed is 100 Mbps.
Make sure that you are using the correct device drivers, supplied with your
v
server.
Check for operating system-specific causes for the problem.
Make sure that the device drivers on the client and server are using the same
protocol.
Test the Ethernet controller.
How 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
Yo u can use the following troubleshooting chart to find solutions to 10/100 Mbps
Ethernet controller problems that have definite symptoms.
Table 1. Ethernet troubleshooting chart
Ethernet controller problem Suggested Action
The server stops running
when loading device drivers.
Ethernet Link Status light
does not light.
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
function well when they share an interrupt with a dissimilar PCI device. Tr y
changing the IRQ assigned to the Ethernet controller or the other device. For
example, for NetWare Versions 3 and 4 it is recommended that disk controllers not
share interrupts with LAN controllers.
Make sure that you are using the most recent device driver available from the
World Wide Web.
Run the network diagnostic program.
Check the following:
Make sure that the hub is turned on.
Check all connections at the Ethernet controller and the hub.
Check the cable. A crossover cable is required unless the hub has an X
designation.
Use another port on the hub.
the hub does not support auto-negotiation, manually configure the Ethernet
controller to match the hub.
you manually configured the duplex mode, make sure that you also manually
configure the speed.
Run diagnostics on the LEDs.
Diagnostics
19
v
v
v
v
v
v
to
v
v
v
v
v
v
v
v
or
v
v
v
is
20
Table 1. Ethernet troubleshooting chart (continued)
Ethernet controller problem Suggested Action
The Ethernet
Transmit/Receive Activity
light does not light.
Check the following:
Note: The Ethernet Transmit/Receive Activity LED illuminates only when data is
sent to or by this Ethernet controller.
Make sure that you have loaded the network device drivers.
The network might be idle. Tr y sending data from this workstation.
Run diagnostics on the LEDs.
The function of this LED can be changed by device driver load parameters. If
necessary, remove any LED parameter settings when you load the device drivers.
Data is incorrect or sporadic. 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-inducing sources like
fluorescent lights.
The Ethernet controller
stopped working when
another adapter was added
the server.
Check the following:
Make sure that the cable is connected to the Ethernet controller.
Make sure that your PCI system BIOS is current.
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
function well when they share an interrupt with a dissimilar PCI device. Tr y
changing the IRQ assigned to the Ethernet adapter or the other device.
The Ethernet controller
stopped working without
apparent cause.
Check the following:
Run diagnostics for the Ethernet controller.
Tr y a different connector on the hub.
Reinstall the device drivers. Refer to your operating-system documentation and to
the ServerGuide information.
Ethernet controller messages
The integrated Ethernet controller might display messages from the following
device drivers:
Novell
™
NetWare
™
IntraNetWare Server ODI
NDIS Adapter for level 2.01 (OS/2)
NDIS Adapter for level 4.0 (Windows NT)
™
SCO
UNIX LLI
Novell NetWare or IntraNetWare server ODI driver messages
This section provides explanations of the error messages for the Novell NetWare or
IntraNetWare server ODI driver, and suggested actions to resolve each problem.
Table 2. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller
PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.
Explanation: The user entered an incorrect parameter keyword. Action: Reload
the driver using the correct keyword.
PCNTNW-NW-054 The adapter did not respond to the initialization command.
Explanation: The adapter did not respond when the driver tried to initialize it.
Action: Verify that the Ethernet controller is enabled. If the Ethernet controller
enabled, go to “Starting the diagnostic programs” on page 16 to run the
diagnostic programs.
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
If
Table 2. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller (continued)
PCNTNW-NW-058 The adapter did not respond to the initialization command.
Explanation: The interrupt request (IRQ) setting might not be valid or the
EEPROM information might be incorrect. Action: Make sure the IRQ settings
are correct in the Configuration/Setup Utility program. for information on
setting the interrupt requests.
PCNTNW-NW-066 The cable might be disconnected from the adapter.
Explanation: The cable might be disconnected from the server Ethernet port.
Action: Verify that a cable is connected to the Ethernet port.
PCNTNW-NW-071 The matching virtual adapter could not be found.
Explanation: Yo u tried to load another instance of the driver with a different
I/O address. This new adapter could not be found. Action: Verify that you
installed an IBM Netfinity 10/100 Fault Tolerant Adapter and make sure that
the adapter is seated correctly.
PCNTNW-NW-072 A resource tag is unavailable.
Explanation: The driver tried to allocate some resources that were not
available. Action: Add more memory, or free some memory resources in the
server. Then, restart the server.
PCNTNW-NW-073 Unable to allocate memory
Explanation: The driver failed to allocate the memory needed for normal
operation. Action: Add more memory, or free some memory resources in the
server. Then, restart the server.
PCNTNW-NW-074 The hardware interrupt cannot be set.
Explanation: An attempt was made to initialize a given hardware interrupt.
The attempt was not successful. Action: Verify that the Ethernet controller is
enabled. If the Ethernet controller is enabled, go to “Starting the diagnostic
programs” on page 16 to run the diagnostic programs.
you have an Ethernet adapter installed, make sure that the adapter does not
share an IRQ with any other device.
PCNTNW-NW-075 The Multiple Link Interface Driver (MLID) cannot be registered with the
Link Support Layer (LSL).
Explanation: An error occurred while the driver was trying to register with the
LSL. Action: Check the version of the NetWare or IntraNetWare Operating
System. Make sure that this driver is correct for the version of NetWare or
IntraNetWare that you are using. Restart the server.
PCNTNW-NW-079 The Multiple Link Interface Driver (MLID) did not initialize MSMTx Free
Count.
PCNTNW-NW-086 The driver parameter block is too small.
PCNTNW-NW-087 The media parameter block is too small.
Explanation: The MSMTx Free Count is not initialized correctly. Action:
Restart the server.
Explanation: The driver parameter block is too small. Action: Restart the
server.
Explanation: The driver media parameter block is too small. Action: Restart
the server.
Diagnostics
21
is
go to
22
Table 2. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller (continued)
PCNTNW-NW-091 The hardware configuration conflicts.
Explanation: Yo u tried to load a new frame type for the existing controller. The
hardware assumptions made in doing so are incorrect. This error can also
occur if you try to specify a mode (such as, redundancy) that conflicts with
another specified mode. Action: Make sure that your hardware configuration
matches the software settings.
PCNTNW-NW-126 The group bit in the node address override was cleared.
Explanation: The IEEE address has a group bit that indicates that an address
belongs to a group of stations. This bit is used only as a destination address; it
cannot be used as a source address. Yo u tried to enter a source address with
this bit set. The driver cleared the group bit of the source address. Action:
None necessary, message is for information only.
PCNTNW-NW-127 The local bit in the node address override was set.
Explanation: The local bit in the IEEE address format indicates that the
addresses are being managed locally. If you use the node address override
capabilities of this driver to enter a new address, the local bit must be set. Yo u
entered an address without the local bit set. The driver has set the local bit.
Action: None necessary, message is for information only.
PCNTNW-NW-164 The device was not found.
Explanation: The driver cannot find an Ethernet controller in the server.
Action: Verify that the Ethernet controller is enabled. If the Ethernet controller
enabled, go to “Starting the diagnostic programs” on page 16 to run the
diagnostic programs.
PCNTNW-NW-165 The device was not found at IOADDRESS.
Explanation: The Ethernet controller cannot be found at the I/O address
specified. Action: The Ethernet controller does not require a parameter for the
I/O address. Remove the I/O address parameter.
PCNTNW-NW-167 PCI scan specified, device not found.
Explanation: The driver cannot locate the Ethernet controller on the PCI bus.
Action: Verify that the Ethernet controller is enabled. If the problem persists,
“Starting the diagnostic programs” on page 16 to run the diagnostic
programs.
PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.
Explanation: The Ethernet controller does not require a DMA setting. Action:
None necessary, message is for information only.
Network driver interface specification 2.01 (OS/2) driver
messages
This section provides explanations of the error messages for the NDIS 2.01 (OS/2)
drivers, and suggested actions to resolve each problem.
Table 3. NDIS 2.01 (OS/2) driver messages for the Ethernet controller
PCNTND-1 Unable to open the Protocol Manager.
Explanation: The NDIS stack is not configured correctly. Action: Check and correct
your configuration.
Hardware Maintenance Manual: xSeries 230 Models 6RY, 61Y
Loading...