IBM 867413x, 867431X, Eserver xSeries 330 Hardware Maintenance Manual
Hard ware Mainte n ance Man u al
xSeries 330 Type 8674, IntelliStation R
Pro Type 6851, and
Network Equipment Building System Type
8674
Hard ware Mainte n ance Man u al
xSeries 330 Type 8674, IntelliStation R
Pro Type 6851, and
Network Equipment Building System Type
8674
First Edition (July 2001)
The following paragraph does not apply to the United Kingdom or to any country where such provisions are
inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do
not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not
apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time.
This publication was developed for products and services offered in the United States of America. IBM may not
offer the products, services, or features discussed in this document in other countries, and the information is subject
to change without notice.
Consult your local IBM representative for information on the products, services, and features available in your area.
Requests for technical information about IBM products should be made to your IBM reseller or IBM marketing
representative.
© Copyright International Business Machines Corporation 2001. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
About this manual
This manual contains diagnostic information, a Symptom-to-FRU index, service
information, error codes, error messages, and configuration information for the
IBM°
8674, and IntelliStation R Pro Type 6851.
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 330 Type 8674/Network Equipment Buildng Systems Type
IBM PC Server products. Before servicing an IBM product, be sure to
review “Safety information” on page 147.
Prenez connaissance de toutes les consignes de type Attention et
© Copyright IBM Corp. 2001 iii
Danger avant de procéder aux opérations décrites par les instructions.
Lesen Sie alle Sicherheitshinweise, bevor Sie eine Anweisung ausführen.
Accertarsi di leggere tutti gli avvisi di attenzione e di pericolo prima di effettuare
qualsiasi operazione.
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a
cabo cualquier operación.
Online support
Use the World Wide Web (WWW) to download Diagnostic, BIOS Flash, Device
Driver files and documents.
The Web address is:
http://www.ibm.com/pc/support
iv Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Contents
About this manual ..........iii
Important safety information ........iii
Online support .............iv
General checkout ..........1
General information .........3
Features and specifications..........4
What the xSeries 330 / IntelliStation R Pro offers . . 5
Reliability, availability, and serviceability features . . 5
Servercontrolsandindicators ........6
Frontview..............6
Rearview..............7
Turning on the server ..........8
Turning off the server ..........9
Stand-by mode ...........9
Diagnostics.............11
Diagnostic tools overview .........11
POST ................12
POST error messages ..........12
Event/errorlogs............12
Small computer system interface messages ....12
Identifying problems using status LEDs .....13
Light Path Diagnostics..........13
Diagnostics panel ..........14
Diagnostic programs and error messages ....15
Textmessages ............15
Starting the diagnostic programs ......16
Viewing the test log ..........16
Recovering BIOS ............18
Troubleshooting the Ethernet controller .....19
Network connection problems .......19
Ethernet controller troubleshooting chart . . . 19
Ethernet controller messages.........20
NDIS 4.0 (Windows NT) driver messages . . . 20
Power checkout .............22
Replacing the battery ...........25
Temperature checkout ...........25
Configuration ............27
Using the Configuration/Setup Utility program . . 27
Starting the Configuration/Setup Utility program 27
Choices available from the Configuration/Setup
mainmenu.............27
Usingpasswords...........31
Power-onpassword .........31
Administrator password ........32
Using the SCSISelect utility program ......33
Starting the SCSISelect utility program ....33
Choices available from the SCSISelect menu . . 34
Using the PXE boot agent utility program . . . 34
Starting the PXE Boot Agent Utility program 35
PXE Boot Agent Utility menu choices....35
Advanced System Management .......36
Updating the ASM firmware .......36
ASM Firmware Update Utility diskette menu
choices ...............37
HardwareStatusandInformation.....37
Configuration Settings .........37
Update System Management Firmware . . . 38
Exit...............38
Configuring the ASM processor ......38
Installing options ..........41
Notices and statements used in this book ....41
Major components of the xSeries 330 ......42
Major components of the R Pro computer ....43
System board..............44
System board options connectors ......44
System board LEDs...........45
Before you begin ............45
System reliability considerations ......46
Working inside a server/workstation with power
on................46
Rackinstallation.............46
Removingthecover...........48
Working with adapters in the xSeries 330 ....49
Adapter considerations .........49
Installing an adapter ..........50
Working with adapters in the R Pro ......53
Adapter considerations .........53
Removing an adapter ..........54
Installing an adapter ..........54
The IBM Remote Supervisor Adapter ......56
Installation prerequisites .........56
Installationrequirements.........57
Remote Supervisor Adapter features .....57
About your documentation ........58
System requirements .........58
Starting the IBM Documentation Browser . . 59
Using the IBM Documentation Browser . . . 59
Unpacking and verifying components ....60
Inventory checklist ..........60
Remote Supervisor Adapter components . . 62
Installing the Remote Supervisor Adapter ....62
Connecting the power-supply adapter .....65
Connecting the LAN and serial port cables ....66
CablingtheEthernetLANport.......67
Cabling the serial (COM) port .......68
Updating the Remote Supervisor Adapter firmware 68
Configuring your system to enable remote access to
the Remote Supervisor Adapter........71
Configuring the Ethernet settings ......71
Configuring the serial port ........73
Setting up point-to-point protocol ......74
Completing the installation .........76
Planning and cabling your interconnect network . . 77
Forwarding alerts ...........77
© Copyright IBM Corp. 2001 v
CablingfortheASMinterconnectnetwork....78
Installing the ASM Interconnect module on the
xSeries 330 .............79
ASM interconnect network configuration examples 80
Harddiskdrives ............82
Preinstallation steps ..........83
Installing or replacing a hard disk drive ....83
Memory...............84
Installing memory modules........85
Microprocessor .............87
Installing the microprocessor .......88
Removing a microprocessor ........90
Fan assembly replacement .........92
Installing the cover ............93
I/O connector locations and ports in the R Pro . . 94
Input/Output ports ..........94
Console ports............95
Device breakout cable .........95
Using the computer as a remote console . . . 96
Serial port .............96
Universal Serial Bus ports .......97
Ethernetports...........98
Advanced System Management ports . . . 101
Audio ports ............102
Videoports............102
I/O connector locations and ports on the xSeries
330.................102
Input/Output ports ..........103
Serial port ............103
Universal Serial Bus ports .......104
Ethernetports...........104
Advanced System Management ports . . . 108
Workingwithcables...........108
Cabling the RS-485 connectors .......109
Connecting servers with a C2T chain ....110
Testing the C2T chain..........111
UsingC2T.............112
Cable management ..........112
FRU information (service only) ....113
Diskette/CD-ROM drives .........113
Diskette/CD-ROM drive bracket .......114
Harddiskdrivebackplane.........115
Power supply .............115
PCI riser card .............116
System board .............116
Important Instructions for the IntelliStation R
Pro (Type 6851) ............117
Initializing the system board ......117
Symptom-to-FRU index .......119
Beepsymptoms ............119
NoBeepsymptoms...........121
Information panel system error LED......122
Diagnostic error codes ..........123
Errorsymptoms............125
POST error codes ............127
SCSI error codes ............131
Temperatureerrormessages........131
Fanerrormessages...........132
System shutdown ............132
Voltage related system shutdown ......132
Temperature related system shutdown ....133
DASD checkout ............133
Bus fault messages ...........134
Undetermined problems..........134
Parts listing, xSeries 330 ......137
System ...............138
Keyboards ..............140
Powercords.............141
IntelliStation R Pro ...........143
Keyboards ..............144
Powercords.............144
Related service information .....147
Safety information............147
General safety ............147
Electrical safety............148
Safety inspection guide .........149
Handling electrostatic discharge-sensitive
devices ..............150
Grounding requirements ........151
Safety notices (multi-lingual translations) . . . 179
Send us your comments! .........180
Problem determination tips .........181
Notices ...............181
Trademarks..............182
vi Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
General checkout
The server/workstation diagnostic programs are stored in upgradable read-only
memory (ROM) on the system board. These programs are the primary method of
testing the major components of the server/workstation: 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 15.
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 147.
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 127.
5. For intermittent problems, check the error log; see “Event/error logs” on
page 12.
© Copyright IBM Corp. 2001 1
001 IS THE SYSTEM PART OF A CLUSTER?
YES. Schedule maintenance with the customer. Shut down all
systems related to the cluster. Run storage test.
NO. Go to step 002.
002 IF THE SYSTEM IS NOT PART OF A CLUSTER:
v Power-off the computer and all external devices.
v Check all cables and power cords.
v Set all display controls to the middle position.
v Power-on all external devices.
v Power-on the computer.
v If the computer hangs and no error is displayed, go to
“Undetermined problems” on page 134.
v Record any POST error messages displayed on the screen. If an
error is displayed, look up the first error in the “POST error
codes” on page 127.
v Check the information LED panel System Error LED; if on, see
“Information panel system error LED” on page 121.
v Check the System Error Log. If an error was recorded by the
system, see “Symptom-to-FRU index” on page 119.
v Start the Diagnostic Programs. See “Diagnostic programs and
error messages” on page 15.
v Check for the following responses:
1. One beep.
2. Readable instructions or the Main Menu.
003 DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
NO. Find the failure symptom in“Symptom-to-FRU index” on
page 119.
YES. Run the Diagnostic Programs. If necessary, refer to “Starting
the diagnostic programs” on page 16.
If you receive an error, go to “Symptom-to-FRU index” on
page 119.
If the diagnostics completed successfully and you still suspect a
problem, see “Undetermined problems” on page 134.
2 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
General information
The IBM®®xSeries 330/IntelliStation®R Pro server/workstation is a one U-high
1
rack-model server/workstation for high-volume network transaction processing.
This high-performance, symmetric multiprocessing (SMP) server/workstation is
ideally suited for networking environments that require superior microprocessor
performance, efficient memory management, flexibility, and reliable data storage.
The xSeries 330/IntelliStation R Pro server/workstation comes with a three-year
limited warranty and IBM server/workstation Start Up Support. If you have access
to the World Wide Web, you can obtain up-to-date information about your xSeries
330 or IntelliStation R Pro model and other IBM server/workstation 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. 2001
3
Features and specifications
The following table provides a summary of the features and specifications for the
xSeries 330, IntelliStation R Pro, and Network Equipment Building System servers.
Table 1. Features and Specifications
Microprocessor:
®
v Intel
v 512 KB Level-2 cache
v Supports up to two
Memory:
v Standard: 256 MB
v Maximum: 4 GB
v Type: 133 MHz, ECC, SDRAM,
v Slots: 4 dual inline
Drives standard:
v Diskette: 1.44 MB
v CD-ROM: 24X IDE
Expansion bays:
v Two 3.5-inch slim high bays for
PCI expansion slots:
v Two 33 MHz/64-bit
Power supply:
One 200 watt (115-230 Vac)
Video:
v S3 Savage4 PRO Graphics/Video
v Compatible with SVGA
v 8 MB SDRAM video memory
Heat output:
Approximate heat output in British
Thermal Units (BTU) per hour
v Minimum configuration: 273 BTU
v Maximum configuration: 751 BTU
Pentium®III
microprocessor with MMX
technology and SIMD extensions
microprocessors
Registered DIMMs
LVD SCSI or IDE (depending on
model) hard disk drives
Accelerator (integrated on system
board)
(80 watts)
(220 watts)
™
Size:
v Height 43.69 mm (1.72″)
v Depth: 653.29 mm (25.72″)
v Width: 439.93 mm (17.32″)
v Weight: approximately 12.7 kg
(28lb) when fully configured
Integrated functions:
v Advanced System Management
processor
v One Ultra160 SCSI controller
v Two 10BASE-T/100BASE-TX Intel
Ethernet controllers
v Two Universal Serial Bus (USB)
ports
v Two RS-485 Advanced System
Management processor ports (one
In, one Out)
v One serial port
v Two Cable Chaining Technology
ports (IN, OUT)
Acoustical noise emissions:
v Sound power, idling: 6.1 bel
maximum
v Sound power, operating: 6.2 bel
maximum
Electrical input:
v Sine-wave input (50-60 Hz)
required
v Input voltage low range:
– Minimum: 100 V ac
– Maximum: 127 V ac
v Input voltage high range:
– Minimum: 200 V ac
– Maximum: 240 V ac
v Input kilovolt-amperes (kVA)
approximately:
– Minimum: 0.08 kVA
– Maximum: 0.22 kVA
Environment (xSeries 330 and
IntelliStation R Pro models):
v Air temperature:
– Server on: 10° to 35° C (50.0° to
95.0° F). Altitude: 0 to 914 m
(2998.7 ft.)
– Server on: 10° to 32° C (50.0° to
89.6° F). Altitude: 914 m (2998.7
ft.) to 2133 m (6998.0 ft.)
– Server off: 10° to 43° C (50.0° to
109.4° F). Maximum altitude: 2133
m (6998.0 ft.)
v Shipping altitude: 0 to 10,668m
(35,000ft)
v Storage temperature: 1° Cto60° C
(34° to 140° F)
v Shipping temperature: -40C to 60C
(-40F to 140F)
v Humidity:
– Server on: 8% to 80%
non-condensing
– Server off: 8% to 80%
non-condensing
v Storage humidity: 5 to 80%
v Shipping humidity: 5 to 100%
v Operating vibration: 0.27G RMS at
5Hz to 500Hz for 30 minutes
v Storage vibration: 0.5G at 2Hz to
200Hz for 15 minutes (all faces);
1.04GRMS Random for 15 minutes
(all faces)
v Operating shock: 3.5G for 3ms
v Storage shock: 50Gwith a velocity
change of 3860mm/sec (all faces)
Environment (NEBS - Network
Equipment Building System models):
v System on:
– Temperature: 5.0° to 40° C (41.0°
to 104.0║ F). Altitude: -60 to 1800
m (-197 to 5,905.0 ft.)
– Relative humidity: 5% to 85%
– Maximum altitude: 4,000 m
(13,123.0 ft.)
v System off:
– Temperature: 5.0 to 40° C (41.0° to
104.0° F). Altitude: -60 to 1800 m
(-197 to 5,905.0 ft.)
– Relative humidity: 5% to 85%
– Maximum altitude: 4,000 m
(13,123.0 ft.)
4 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
What the xSeries 330 / IntelliStation R Pro offers
The unique design of this server takes advantage of advancements in symmetric
multiprocessing (SMP), data storage, and memory management. The server
combines:
v Impressive performance using an innovative approach to SMP
The server supports up to two Pentium III microprocessors. The server comes
with one microprocessor installed; you can install an additional microprocessor
to enhance performance and provide SMP capability.
v Large system memory
The memory bus in the server supports up to 4 gigabytes (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,
synchronous-dynamic-random access memory (SDRAM) dual inline memory
modules (DIMMs).
v System-management capabilities
The server comes with an Advanced System Management Processor on the
system board. This processor, in conjunction with the systems-management
software that is provided with the server, enables you to manage the functions
of the server locally and remotely. The Advanced System Management Processor
also provides system monitoring, event recording, and dial-out alert capability.
Note: The Advanced System Management Processor is sometimes referred to as
the service processor.
Refer to the documentation provided with the system-management software for
more information.
v Integrated network environment support
The server comes with two Ethernet controllers on the system board. Each
Ethernet controller has an interface for connecting to 10-Mbps or 100-Mbps
networks. The server automatically selects between 10BASE-T and 100BASE-TX.
Each controller provides full-duplex (FDX) capability, which allows simultaneous
transmission and reception of data on the Ethernet local area network (LAN).
v IBM ServerGuide CDs
The ServerGuide CDs that are included with the 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.
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.
v Menu-driven setup, system configuration, RAID configuration, and diagnostic
programs
v Power-on self-test (POST)
v Integrated Advanced System Management Processor
General information 5
v Predictive Failure Alerts (PFA)
v Remote system problem-analysis support
v Power and temperature monitoring
v Hot-swap drive bays
v Error codes and messages
v System error logging
v Upgradable BIOS, diagnostics, and Advanced System Management Processor
code
v Automatic restart after a power failure
v Parity checking on the PCI buses
v CRC checking on the SCSI buses
v Error checking and correcting (ECC) memory
v Redundant Ethernet capabilities
v Light Path Diagnostics on the system board
v Vital Product Data (VPD) on system board, and SCSI backplane
Server controls and indicators
This section identifies the controls and indicators on the front and the back of your
server.
Front view
Power control
button
Power-on
light (green)
Reset
button
Select
button/indicator
(green)
System error
light (amber)
Diskette drive
activity light
(green)
Diskette eject
button
Hard disk drive
status light (amber)
light (green)
CD eject buttonCD activity
Hard disk drive
activity light (green)
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 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.
Select button/indicator: Press this button to select the server in the C2T chain. The
green LED on this button lights when the monitor, keyboard, and mouse are
logically connected to this server.
System-error light: This amber LED lights when a system error occurs. An LED on
the Light Path Diagnostic panel on the system board will also be on to further
isolate the error.
Diskette drive activity light: When this LED is on, it indicates that the diskette
drive is in use.
6 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Diskette-eject button: Push this button to release a diskette from the drive.
Hard disk drive status light: Each of the hot-swap drives has a hard disk drive
status light. When this amber LED is on continuously, the drive has failed. This
status light is active only with a ServeRAID adapter installed in the server.
Hard disk drive activity light: Each of the hot-swap drives has a Hard Disk
Activity light. When this green LED is flashing, the controller is accessing 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.
Rear view
Ethernet 1 speed
indicator (green)
Ethernet 1 link
indicator (green)
C2T IN port
Advanced systems
management RS-485
Select light (green)
Ethernet 2 speed
indicator (green)
Ethernet 2 link
indicator (green)
Power-on light
(green)
USB 2
USB 1
System error
light (amber)
Serial port
C2T OUT port
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.
Ethernet 1 link indicator: This green LED lights when there is an active link
connection on the 10BASE-T or 100BASE-TX interface for Ethernet port 1.
Advanced system management: The RS-485 ports (in and out) are used for
creating a system management bus between several servers.
Select light: This green LED lights when the monitor, keyboard, and mouse are
logically connected to this server. This light duplicates the Select button LED on
the front of the server.
Cable Chaining Technology OUT: This port is used to connect the server to a
keyboard, monitor, and pointing device. It is also used to connect multiple servers
together to share a single keyboard, monitor, and pointing device.
Serial port: Signal cables for modems or other serial devices connect here to the
9-pin serial port connector.
Cable Chaining Technology IN: This port is used to connect multiple servers
together to share a single keyboard, monitor, and pointing device.
USB 2 Universal Serial Bus 2
General information 7
USB 1: Universal Serial Bus 1
System-error light: This amber LED lights when a system error occurs. An LED on
the Light Path Diagnostic panel on the system board may also be on to further
isolate the error. This light duplicates the system error light on the front of the
server.
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.
Ethernet 2 link indicator: This green LED lights when there is an active link
connection on the 10BASE-T or 100BASE-TX interface for Ethernet port 2.
Ethernet 2 speed indicator: This green LED lights when the speed of the Ethernet
LAN connected to Ethernet port 2 is 100 Mbps.
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 then press the power control button on the front of the server.
v You can press the Power control button on the front of the server to start the
server.
Note: After you plug the power cord of your server into an electrical outlet,
wait approximately 30 seconds before pressing the Power control button.
During this time, the system-management processor is initializing and the
Power control button does not respond.
v If the server is turned on and a power failure occurs, the server will start
automatically when power is restored.
v The Advanced System Management Processor can also turn on the server.
CAUTION:
The power control button on the device and the power switch on the power supply (if
there is one) 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.
8 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
2
1
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.
Note: Each operating system is different. Some will allow an immediate
shut-down, while others require and orderly shut-down procedure.
2. Press the power control button on the front of the server. This will put the
server in the stand-by mode.
3. Disconnect the server from the power source.
Note: After turning off the server, wait at least 5 seconds before you turn on
the server again.
Stand-by mode
Stand-by puts the server in a wait state. When in a wait state, the server is not
running the operating system, and all core logic is shut down, except for the
service processor.
Complete the following steps to put the server into stand-by mode:
1. Refer to your operating system documentation for the proper procedure to
shut-down the operating system.
Note: Each operating system is different. Read all the documentation about
shutting down the operating system before continuing.
2. Press the power control button on the front of the server.
General information 9
10 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with the server/workstation.
Diagnostic tools overview
The following tools are available to help you identify and resolve hardware-related
problems:
v 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” on page 12
for more information.
v Diagnostic programs and error messages
The server/workstation 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/workstation. See “Diagnostic
programs and error messages” on page 15 for more information.
v Light Path Diagnostic
The Light Path Diagnostic is used to quickly identify system errors.
© Copyright IBM Corp. 2001 11
POST
When you turn on the server/workstation, it performs a series of tests to check the
operation of server/workstation components and some of the options installed in
the server/workstation. This series of tests is called the power-on self-test or POST.
If POST finishes without detecting any problems, a single beep sounds and the
first screen of your operating system or application program appears.
If POST detects a problem, more than one beep sounds and an error message
appears on your screen. See “POST error messages” for more information.
™
Notes
1. If you have a power-on password set, you must type the password and press
2. A single problem might cause several error messages. When this occurs, work
:
Enter, when prompted, before POST will continue.
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 error messages
The table “POST error codes” on page 127 provides information about the POST
error messages that can appear during startup.
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
messages issued during POST and all system status messages from the Advanced
System Management Processor.
To view the contents of this error log, start the Configuration/Setup Utility
program; then, select Event/Error Logs from the main menu.
Small computer system interface messages
The following table lists actions to take if you receive a SCSI error message.
Note: If the server/workstation does not have a hard disk drive, ignore any
message that indicates that the drive is not installed.
You will get these messages only when running the SCSISelect Utility. See “SCSI
error codes” on page 131.
12 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Table 2. SCSI messages
SCSI Messages Description
All One or more of the following might be causing the problem.
v A failing SCSI device (adapter, drive, controller)
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/workstation.
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. If the error remains or
recurs, call for service.
Identifying problems using status LEDs
If the System Error light in the operator information panel on the front of the
server/workstation is on, one or more LEDs inside the server/workstation may be
on. Use the light path diagnostics to identify the type of error that occurred.
For LED locations see “System board LEDs” on page 45.
Light Path Diagnostics
You can use the Light Path Diagnostics built into your server/workstation to
quickly identify the type of system error that occurred. The Light Path Diagnostics
panel is located on the system board just behind PCI adapter slot 1. When you
press on the Light Path Diagnostics button the LED on the top right corner of the
panel will illuminate. This shows that the diagnostic circuitry is working correctly.
Your server/workstation is designed so that any LEDs that are illuminated can be
re-illuminated without AC power after you remove the cover. This feature helps
you isolate the problem if an error causes the server/workstation to shut down.
See Table 3 on page 14.
Important: You have up to 12 hours to use the Light Path Diagnostic LED’s after
AC power has been removed from the server/workstation. After 12 hours you
must power the server/workstation up again to be able to use the Light Path
Diagnostic LEDs to help locate system errors.
To view the LEDs on the system board:
1. Turn off the server/workstation and any peripheral devices.
2. Remove the cables.
3. Remove the server/workstation from the rack and place it on a flat,
non-conductive surface.
Diagnostics 13
4. Remove the server/workstation cover (see “Removing the cover” on page 48).
Note: Refer to “Working inside a server/workstation with power on” on
page 46 for instructions and precautions for working in the
server/workstation with the power on.
5. Press and hold the Light Path Diagnostics (blue) button on the diagnostics
panel. The LEDs will illuminate while the switch is pressed.
Note: You can illuminate the LEDs for a maximum of two minutes. After that
time, the circuit that powers the LEDs is exhausted.
Diagnostics panel
The following illustration shows the LEDs on the diagnostics panel on the system
board. See Table 3 for information on identifying problems using these LEDs.
Light
Path
PS
TEMP
FAN
SP
Table 3. Light Path Diagnostics
LED Description
PS Power supply error
MEM Memory error occurred
TEMP System temperature exceeded maximum rating
CPU Microprocessor error
FAN Fan failed or operating slowly
VRM Voltage regulator module error
™
SP
PCI Error occurred on an adapter in PCI slot 1 or 2, or one of the PCI service
MEM
CPU
VRM
PCI
Error occurred on service processor
devices integrated on the system board.
See “Information panel system error LED” on page 121 for appropriate action.
14 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Diagnostic programs and error messages
The server/workstation diagnostic programs are stored in up grad able read-only
memory (ROM) on the system board. These programs are the primary method of
testing the major components of the server/workstation.
Sometimes the first error to occur causes additional errors. In this case, the
server/workstation 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
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
information.
This result occurs when the diagnostic test completes without any
errors.
This result occurs when you stop the diagnostic test before it is
complete.
Not Applicable
This result occurs when you specify a diagnostic test for a device
that is not present.
Diagnostics 15
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
You can press F1 while running the diagnostic programs to obtain Help
information. You also can press F1 from within a help screen to obtain online
documentation from which you can select different categories. To exit Help and
return to where you left off, press ISC.
To start the diagnostic programs:
1. Turn on the server/workstation and watch the screen.
2. When the message F2 for Diagnostics appears, press F2.
3. Type in the appropriate password; then, press Enter.
4. Select either Extended or Basic from the top of the screen.
5. When the Diagnostic Programs screen appears, select the test you want to run
from the list that appears; then, follow the instructions on the screen.
Notes:
a. If the server/workstation stops during testing and you cannot continue,
restart the server/workstation and try running the diagnostic programs
again.
b. The keyboard and mouse (pointing device) tests assume that a keyboard
and mouse are attached to the server/workstation.
c. If you run the diagnostic programs with no mouse attached to the
server/workstation, 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.
d. You 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
Interface test only if there are no USB devices attached.
e. You can view server/workstation configuration information (such as system
configuration, memory contents, interrupt request (IRQ) use, direct memory
access (DMA) use, device drivers, and so on) by selecting Hardware Info
from the top of the screen.
When the tests have completed, you can view the Test Log by selecting Utility
from the top of the screen.
If the hardware checks out OK but the problem persists during normal
server/workstation 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.
16 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Note: If you already are running the diagnostic programs, begin with step 3.
To view the test log:
1. Turn on the server/workstation and watch the screen.
If the server/workstation is on, shut down your operating system and restart
the server/workstation:
2. When the message F2 for Diagnostics appears, press F2.
If a power-on password is set, the server/workstation prompts you for it. Type
in the appropriate password; then, press Enter.
3. When the Diagnostic Programs screen appears, select Utility from the top of
the screen.
4. Select View Test Log from the list that appears; then, follow the instructions on
the screen.
The system maintains the test-log data while the server/workstation is
powered on. When you turn off the power to the server/workstation, the test
log is cleared.
Diagnostics 17
Recovering BIOS
If the BIOS has become corrupted, such as from a power failure during a flash
update, you can recover the BIOS using the BIOS code page jumper and a BIOS
flash diskette.
Note: You can obtain a BIOS flash diskette from one of the following sources:
To recover the BIOS:
™
v Use the ServerGuide
program to make a BIOS flash diskette.
v 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/workstation.
v Contact your IBM service representative.
1. Turn off the server/workstation and peripheral devices and disconnect all
external cables and power cords; then, remove the cover.
2. Locate the BIOS code page jumper (J19) on the system board.
BIOS code
page jumper
(J19)
1 2 3
3. Place a jumper on pins 1 and 2 to enable BIOS back page.
4. Reconnect all external cables and power cords and turn on the peripheral
devices.
5. Insert the BIOS Flash Diskette in the diskette drive.
6. Restart the server/workstation. The system begins the power-on self-test
(POST) and BIOS flash.
18 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
7. Select 1 - Update POST/BIOS from the menu that contains various flash
(update) options.
8. When prompted as to whether you want to save the current code to a
diskette, select N.
9. When prompted to choose a language, select a language (from 0 to 7) and
press Enter to accept your choice.
10. Do not reboot your system at this time.
11. Remove the BIOS Flash Diskette from the diskette drive.
12. Turn the server/workstation off.
13. Move the jumper on J19 to pins 2 and 3 to return to normal startup mode.
14. Restart the server/workstation. 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
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 Make sure that you are using the correct device drivers, supplied with the
server/workstation.
v Check for operating system-specific causes for the problem.
v Make sure that the device drivers on the client and server/workstation are using
the same protocol.
v 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
You can use the following troubleshooting chart to find solutions to 10/100 Mbps
Ethernet controller problems that have definite symptoms.
Diagnostics 19
Table 4. Ethernet troubleshooting chart
Ethernet controller problem Suggested Action
The server/workstation stops
running when loading device
drivers.
Data is incorrect or sporadic. Check the following:
The Ethernet controller
stopped working when
another adapter was added
to the server/workstation.
The Ethernet controller
stopped working without
apparent cause.
The PCI BIOS interrupt settings are incorrect.
Check the following:
v 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. Try
changing the IRQ assigned to the Ethernet controller or the other device. For
example, for NetWare Versions 3 and 4 it is recommended that disk controllers not
share interrupts with LAN controllers.
v Make sure that you are using the most recent device driver available from the
Wo rl d W id e We b.
v Run the network diagnostic program.
v Make sure that you are using Category 5 cabling when operating the
server/workstation at 100 Mbps.
v Make sure that the cables do not run close to noise-inducing sources like
fluorescent lights.
Check the following:
v Make sure that the cable is connected to the Ethernet controller.
v Make sure that your PCI system BIOS is current.
v Reseat the adapter.
v 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. Try
changing the IRQ assigned to the Ethernet adapter or the other device.
Check the following:
v Run diagnostics for the Ethernet controller.
v Try a different connector on the hub.
v Reinstall the device drivers. Refer to your operating-system documentation and to
the ServerGuide information.
Ethernet controller messages
The integrated Ethernet controller might display messages from the following
device drivers:
v NDIS Adapter for level 4.0 (Windows
NDIS 4.0 (Windows NT) driver messages
This section contains the error messages for the NDIS 4.0 drivers. The explanation
and recommended action are included with each message.
Table 5. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller
Error code (hex) Description
0x00 Explanation: The driver could not register the specified interrupt. Action: Using the
Configuration/Setup utility, make sure that a PCI interrupt is assigned to your Ethernet card,
and that Ethernet is enabled.
0x01 Explanation: One of the PCI cards did not get the required resources. Action: Using the
Configuration/Setup utility, make sure that a PCI interrupt is assigned to your Ethernet card,
and that Ethernet is enabled.
20 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
®NT®
)
Table 5. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller (continued)
Error code (hex) Description
0x02 Explanation: Bad node address (multicast address). Action: Make sure the locally administered
address is valid, if one is specified. The address can not be a multicast address.
0x03 Explanation: Failed self-test. Action: Make sure a cable is attached to the Ethernet connector. If
the problem persists, call for service.
0x0D Explanation: Could not allocate enough memory for transmit queues. Action:
1. From the Windows NT desktop, select Start -> Control Panel -> Networks -> Adapters.
2. Select your IBM Ethernet adapter from the list.
3. Select Properties -> Advanced.
4. Lower the resource values that apply to the transmit queue.
0x0E Explanation: Could not allocate enough memory for receive queue. Action:
1. From the Windows NT desktop, select Start -> Control Panel -> Networks -> Adapters.
2. Select your IBM Ethernet adapter from the list.
3. Select Properties -> Advanced.
4. Lower the resource values that apply to the receive queue.
0x0F Explanation: Could not allocate enough memory for other structures. Action:
1. From the Windows NT desktop, select Start -> Control Panel -> Networks -> Adapters.
2. Select your IBM Ethernet adapter from the list.
3. Select Properties -> Advanced.
4. Lower the value for the resource named in the message.
0x10 Explanation: Did not find any Ethernet controllers. Action: Using the Configuration/Setup
utility, make sure that Ethernet is enabled.
0x11 Explanation: Multiple Ethernet controllers found, but none matched the required ID. Action:
Using the Configuration/Setup utility, make sure that Ethernet is enabled.
0x13 Explanation: Did not find any Ethernet controllers that matched the required subven/subdev.
Action: Using the Configuration/Setup utility, make sure that Ethernet is enabled.
0x16 Explanation: Single adapter found but multiple instances tried to load. Action: Using the
Configuration/Setup utility, make sure that Ethernet is enabled, and that the slot containing the
IBM Netfinity 10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI adapter is enabled.
0x17 Explanation: Slot parameter not specified in the registry. Action: Remove the adapter driver and
reinstall it. If the problem persists, call for service.
All other
Action: Call for service.
4-character
hexadecimal
codes
Ethernet teaming messages:
Table 6. NDIS (Windows NT or Windows 2000) driver teaming messages for the Ethernet controller
Event ID Type Description
01 Error Explanation: Team Name and physical adapter name are the same. This
02 Error Explanation: Unable to allocate required resources. Action: Free some
03 Error Explanation: Unable to read required registry parameters. Action:
is an invalid configuration. Action: Reconfigure the adapter team by
double-clicking the PROSet icon in the control panel.
memory resources and restart.
Reconfigure the adapter team by double-clicking the PROSet icon in the
control panel.
Diagnostics 21
Table 6. NDIS (Windows NT or Windows 2000) driver teaming messages for the Ethernet controller (continued)
Event ID Type Description
04 Error Explanation: Unable to bind to physical adapter. Action: Reconfigure the
adapter team by double-clicking the PROSet icon in the control panel.
05 Error Explanation: Unable to initialize an adapter team. Action: Reconfigure
the adapter team by double-clicking the PROSet icon in the control panel.
06 Informational Explanation: Te a m nn. Primary adapter is initialized. Action: None.
07 Informational Explanation: Te a m nn. Secondary adapter is initialized. Action: None.
08 Informational Explanation: Te a m nn. Virtual adapter or Team is initialized. Action:
None.
09 Informational Explanation: Te a m nn. Primary adapter is switching over. Action: None.
10 Warning Explanation: Te a m nn. Adapter link down. Action: Make sure the
adapter is functioning properly.
11 Informational Explanation: Te a m nn. Secondary adapter took over. Action: None.
12 Warning Explanation: Te a m nn. Secondary adapter is deactivated from the Team.
Action: Make sure the secondary adapter is functioning properly and
that the adapter cable is securely connected to the LAN.
13 Informational Explanation: Te a m nn. Secondary adapter has rejoined the Team. Action:
None.
14 Informational Explanation: Te a m nn. Secondary adapter link is up. Action: None.
15 Error Explanation: Te am nn. The last adapter has lost its link. Network
connection has been lost. Action: Shut down the server/workstation and
replace the adapters; then, restart the server/workstation to reestablish
the connection.
16 Informational Explanation: Te a m nn. An adapter has re-established the link. Network
connection has been restored. Action: None.
17 Informational Explanation: Te a m nn. Preferred primary adapter has been detected.
Action: None.
18 Informational Explanation: Te a m nn. Preferred secondary adapter has been detected.
Action: None.
19 Informational Explanation: Te a m nn. Preferred primary adapter took over. Action:
None.
20 Informational Explanation: Te a m nn. Preferred secondary adapter took over. Action:
None.
21 Warning Explanation: Te a m nn. Primary adapter does not sense any Probes.
Possible reason: partitioned Team. Action: Make sure the cables of the
adapter team are connected to the same LAN segment. Reconfigure the
team if necessary.
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 system and disconnect the AC cord(s). Disconnect all external
cables and remove server/workstation from the rack.
22 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674
Loading...