IBM xSeries 330, xSeries 330 8675 Hardware Maintenance Manual
Hard ware Mainte n ance Man u al
xSeries 330 Type 8675
Note: Before using this information and the product it supports, be sure to read the general information under
“Notices” on page 169.
First Edition (February 2002)
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.
Contents
About this manual ..........1
Important safety information .........1
Online support .............2
General checkout ..........3
General information .........5
Features and specifications..........6
What the xSeries 330 offers .........6
Reliability, availability, and serviceability features . . 8
Servercontrolsandindicators ........8
Frontview..............9
Rearview..............10
Turning on the server ..........11
Turning off the server ..........11
Service processor remote terminal features ....12
Connecting to the onboard service processor . . 12
Running remote diagnostics ........13
Special keystrokes ...........14
Considerations when using IBM Remote
Supervisor Adapter ...........14
Diagnostics.............15
Diagnostic tools overview .........15
POST ................16
POST error messages ..........16
Errorlogs..............16
Small computer system interface (SCSI) messages . 16
Identifying problems using status LEDs .....17
Light Path Diagnostics..........17
Diagnostic programs and error messages ....18
Textmessages ............19
Starting the diagnostic programs ......20
Viewing the test log ..........20
Recovering BIOS ............22
Troubleshooting the Ethernet controller .....23
Network connection problems .......23
Ethernet controller troubleshooting chart . . . 23
Ethernet controller error messages .......24
NDIS 4.0 (Windows NT or 2000) driver messages 24
Power checkout .............27
Replacing the battery ...........28
Temperature checkout ...........29
Configuration ............31
Using the Configuration/Setup Utility program . . 31
Starting the Configuration/Setup Utility program 32
Choices available from the Configuration/Setup
mainmenu.............32
Usingpasswords ...........35
WakeonLAN............37
UsingMXTmemory..........37
Using the SCSISelect utility program ......38
Starting the SCSISelect utility program ....38
SCSISelect menu choices .........38
Using the PXE boot agent utility program . . . 39
Updating the ASM firmware and configuring the
ASM processor .............41
Updating the ASM firmware .......41
ASM Firmware Update Utility diskette menu
choices ...............41
Configuring the ASM processor ......43
Updating BiOS or Diagnostics ........44
Installing options ..........45
Major components of the xSeries 330 server . . . 46
System board..............46
System board options connectors ......47
System board LEDs...........48
Before you begin ............48
System reliability considerations ......49
Working inside a server with power on ....49
Rackinstallation.............49
Removingthecover...........51
Working with adapters ..........53
Adapter considerations .........53
Installing an adapter ..........54
The IBM Remote Supervisor Adapter ......57
Installation prerequisites .........57
Installationrequirements.........58
Remote Supervisor Adapter features .....58
Unpacking and verifying components ....60
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
CablingfortheASMinterconnectnetwork....78
Installing the ASM Interconnect module on the
xSeries 330 .............79
ASM interconnect network configuration examples 80
Harddiskdrives ............82
Harddiskdriveconsiderations.......83
Installing or replacing a hot-swap SCSI hard disk
drive ...............83
Workingwithmemory ..........84
About MXT memory ..........85
Memoryconsiderations.........85
Installing a microprocessor .........88
Replacing a fan assembly ..........91
© Copyright IBM Corp. 2001 iii
Installing the cover ............93
Input/output ports and connectors ......93
Serial port and connector .........94
Universal Serial Bus ports ........95
C2Tports..............95
C2T breakout cable ...........97
Ethernetports............99
Advanced System Management ports ....102
Rackinstallationconsiderations.......103
Workingwithcables...........104
Cabling the RS-485 connectors.......104
Connecting servers with a C2T chain ....105
Testing the C2T chain .........106
UsingC2T.............107
Cable management ..........108
FRU information (service only) ....109
Diskette/CD-ROM drives .........109
Diskette/CD-ROM drive bracket .......110
Harddiskdrivebackplane.........111
Power supply .............111
PCI riser card .............112
System board .............112
Symptom-to-FRU index .......113
Beepsymptoms ............113
NoBeepsymptoms...........115
Information panel system error LED ......115
Diagnostic error codes ..........117
Errorsymptoms............120
POST error codes ............121
SCSI error codes ............125
Temperatureerrormessages........125
Fanerrormessages...........126
System shutdown ............126
Voltage related system shutdown ......126
Temperature related system shutdown ....126
DASD checkout ............127
Bus fault messages ...........127
Undetermined problems..........128
Parts listing ............129
xSeries 330 ..............130
Keyboards ..............132
Powercords.............133
Related service information .....135
Safety information............135
General safety ............135
Electrical safety............136
Safety inspection guide .........137
Handling static-sensitive devices ......138
Grounding requirements ........139
Safety notices (multi-lingual translations) . . . 139
Send us your comments! .........168
Problem determination tips .........169
Notices ...............169
Trademarks..............170
iv Hardware Maintenance Manual: xSeries 330 Type 8675
About this manual
This manual contains diagnostic information, a Symptom-to-FRU index, service
information, error codes, error messages, and configuration information for the
«
IBM
Important: This manual is intended for trained servicers who are familiar with
Important safety information
Be sure to read all caution and danger statements in this book before performing
any of the instructions.
Leia todas as instruções de cuidado e perigo antes de executar qualquer operação.
xSeries 330 Type 8675.
IBM PC Server products. Before servicing an IBM product, be sure to
review “Safety information” on page 135.
Prenez connaissance de toutes les consignes de type Attention et
Danger avant de procéder aux opérations décrites par les instructions.
© Copyright IBM Corp. 2001 1
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
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a
cabo cualquier operación.
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
2 Hardware Maintenance Manual: xSeries 330 Type 8675
General checkout
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 a server. Major components that can be tested include the system
board, Ethernet controller, video controller, RAM, keyboard, mouse (pointing
device), diskette drive, serial ports, hard drives, and parallel ports. Not all servers
include all these items; your hardware may differ. You can also use them to test
some external devices. See “Diagnostic programs and error messages” on page 18.
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 135.
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 121.
5. For intermittent problems, check the error log; see “Error logs” on page 16.
1. IS THE SYSTEM PART OF A CLUSTER?
YES. Schedule maintenance with the customer. Shut down all systems related to
the cluster. Run storage test.
NO. Go to step 2.
2. 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.
© Copyright IBM Corp. 2001 3
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 128.
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 121.
v Check the information LED panel System Error LED; if on, see “Information
panel system error LED” on page 115.
v Check the System Error Log. If an error was recorded by the system, see
“Symptom-to-FRU index” on page 113.
v Start the Diagnostic Programs. See “Diagnostic programs and error
messages” on page 18.
v Check for the following responses:
a. One beep.
b. Readable instructions or the Main Menu.
3. DID YOU RECEIVE BOTH OF THE CORRECT RESPONSES?
NO. Find the failure symptom in“Symptom-to-FRU index” on page 113.
YES. Run the Diagnostic Programs. If necessary, refer to “Starting the diagnostic
programs” on page 20.
If you receive an error, go to “Symptom-to-FRU index” on page 113.
If the diagnostics completed successfully and you still suspect a problem, see
“Undetermined problems” on page 128.
4 Hardware Maintenance Manual: xSeries 330 Type 8675
General information
The IBM
®
xSeries 330 Type 8675 is a one U-high1rack model server for
high-volume network transaction processing. This high-performance, symmetric
multiprocessing (SMP) server is ideally suited for networking environments that
require superior microprocessor performance, flexibility, reliable data storage, and
efficient memory management.
™
The xSeries 330 contains several IBM X-Architecture
technologies, which help
increase server performance and reliability. The X-Architecture technologies
provided in your server model include two of the most recent advancements in
memory management technologies.
v IBM Memory eXpansion Technology (MXT) on the xSeries 330 Type 8675
effectively expands the memory capacity of the server when an MXT-aware
operating system is running on the server.
Note: An MXT device driver supporting your operating system might be
required before MXT can be used.
™
v IBM Chipkill
Memory technology protects the system from a single chip failure
on a dual inline memory module (DIMM).
If you have access to the World Wide Web, you can obtain up-to-date information
about the server and other IBM server products at
http://www.ibm.com/eserver/xseries.
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
5
Features and specifications
The following table provides a summary of the features and specifications for the
xSeries 330 server.
Table 1. Features and Specifications
Microprocessor:
®
v Intel
v 133 MHz front-side bus (FSB)
v 512 KB Level-2 processor cache
v Supports up to two
Memory:
v Memory eXpansion Technology
v Standard: 512 MB in DIMMs (up
v Maximum: 4 GB in DIMMs (up to
v Type: 133 MHz, ECC, SDRAM,
v Sizes: 256 MB, 512 MB, or 1 GB
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 One 33 MHz/64-bit, 5.0 V, half
v One 66 MHz/64-bit, 3.3 V, full
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
Pentium®III
microprocessor, 1.4 GHz
microprocessors
(MXT) controller chip
to1GBMXTmemory)
8GBMXTmemory)
Registered x4 (Chipkill) DIMMs
DIMMs
hard disk drives
length
length
Accelerator (integrated on system
board)
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 with support for IBM
Remote Supervisor Adapter
v One Ultra160 SCSI controller
v Two 10BASE-T/100BASE-TX Intel
Ethernet controllers with support
for Wake on LAN
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
(C2T) ports (one In, one Out)
Acoustical noise emissions:
v Sound power, idling: 6.2 bel
maximum
v Sound power, operating: 6.2 bel
maximum
v Sound pressure, idling: 47 decibels
v Sound pressure, operating: 47
decibels
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:
v Air temperature:
– Server on: 10° to 35° C (50.0° to
95.0° F). Altitude: 0 to 914 m
(2998.7 ft.)
– Server on: 10° to 32° C (50.0° to
89.6° F). Altitude: 914 m (2998.7
ft.) to 2133 m (6998.0 ft.)
– Server off: 10° to 43° C (50.0° to
109.4° F). Maximum altitude: 2133
m (6998.0 ft.)
v Humidity:
– Server on: 8% to 80%
™
– Server off: 8% to 80%
Heat output:
Approximate heat output in British
Thermal Units (BTU) per hour
v Minimum configuration: 273 BTU (80
watts)
v Maximum configuration: 751 BTU
(220 watts)
What the xSeries 330 offers
The unique design of this server takes advantage of advancements in symmetric
multiprocessing (SMP), data storage, and memory management. The server
combines:
v IBM X-Architecture
6 Hardware Maintenance Manual: xSeries 330 Type 8675
™
IBM’s X-Architecture leverages proven innovative IBM technologies to build the
most powerful, scalable, reliable Intel-processor-based servers in the world.
X-Architecture includes features such as Light Path Diagnostics
™
, Predictive
Failure Analysis®, and the Advanced System Management processor.
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 GB. 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). The memory
controller also provides Chipkill Memory protection. Chipkill Memory protection
is a technology that protects the system from a single chip failure on a DIMM.
The IBM Memory eXpansion Technology (MXT) chip on your server enables you
to store up to nearly twice the amount of data in system memory as was
previously possible. The MXT technology enables increased system performance
(through more available memory) without increasing system memory, or
comparable performance with half the memory. The level of increase
performance can depend on the number of applications running on the system
and the load on the system.
Notes:
1. An MXT device driver supporting the operating system might be required.
The IBM MXT device driver for Microsoft
the ServerGuide
™
CD. Use the ServerGuide CDs to install the MXT device
®
Windows®2000 is available on
driver, or download and install the latest device driver from
http://www.ibm.com/pc/support/ on the World Wide Web. The Red Hat
®
Linux
7.2 operating system includes MXT support natively, and does not
need a separate device driver.
2. With non-MXT-aware operating systems, the system memory is limited to the
sum of the DIMMs installed.
3. On an MXT-aware Microsoft Windows operating system, MXT support
software limits Windows Address Windowing Extensions (AWE) allocations
to approximately one-half the physical memory size (one-fourth the MXT
memory). Because Windows AWE pages are nonpageable, this restriction
prevents user applications from running out of MXT memory. This is not a
problem for most applications.
4. Device drivers must limit the locked pages count to less than the physical
memory size. Most device drivers will operate with this restriction.
v System-management capabilities
The server comes with an Advanced System Management (ASM) processor on
the system board. This processor, in conjunction with the system-management
software that is provided with the server, enables you to manage the functions
of the server locally and remotely. The ASM processor also provides system
monitoring, event recording, and dial-out alert capability.
Note: The ASM processor is sometimes referred to as the service processor.
The optional IBM Remote Supervisor Adapter works in conjunction with the
integrated service processor to give you a World Wide Web interface to the
system-management functions. You can manage your server over the Internet or
intranet.
General information 7
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.
For more information about the ServerGuide CDs, see the documentation
provided with the ServerGuide software.
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 ASM processor
v Predictive Failure Analysis
v Remote system problem-analysis support
v Power and temperature monitoring
v Hot-swap drive bays (some models only)
v Error codes and messages
v System error logging
v Upgradable BIOS, diagnostics, and ASM Processor code
v Automatic restart after a power failure
v CRC checking on the SCSI buses
v Error checking and correcting (ECC) memory
v Chipkill Memory
v Redundant Ethernet capabilities
v Light Path Diagnostics
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.
®
(PFA)
™
on the system board and SCSI backplane
8 Hardware Maintenance Manual: xSeries 330 Type 8675
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
light (green)
CD eject buttonCD activity
Power-control button: Press this button to manually turn the server on or off.
Power-on light: This green LED lights and stays on when you turn on your server
and 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.
Diskette-eject button: Push this button to release a diskette from the drive.
CD-eject button:Push this button to release a CD from the drive.
CD-ROM drive activity light: When this light is on, it indicates that the CD-ROM
drive is in use.
General information 9
Rear view
Ethernet 1 speed
indicator (green)
Ethernet 1 link
indicator (green)
Ethernet 2 link
indicator (green)
Ethernet 2 speed
indicator (green)
Advanced System
Management RS-485 connectors
C2T (Out) connector
Select light (green)
USB 2
connector
Power-on
light (green)
USB 1
connector
System error
light (amber)
Serial connector
C2T (In) connector
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 connectors: The RS-485 connectors 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.
C2T (Out) connector: 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 connector: Signal cables for modems or other serial devices connect here to
the 9-pin serial port connector.
C2T (In) connector: This port is used to connect multiple servers together to share
a single keyboard, monitor, and pointing device.
USB 2 connector: This connector is used to attach USB devices to Universal Serial
Bus port 2.
USB 1 connector: This connector is used to attach USB devices to Universal Serial
Bus port 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.
10 Hardware Maintenance Manual: xSeries 330 Type 8675
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.
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:
Statement 5
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.
2
1
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 into Standby 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.
General information 11
Standby mode
Standby 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 standby 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.
Service processor remote terminal features
You can connect to the service processor from another computer in order to
perform remotely the following system functions on your server:
v POST
v Setup
v Diagnostics
v Screen capture
v View error log
v Flash update the BIOS code and service processor code
Connecting to the onboard service processor
You can establish a connection from the remote system to the server onboard
service processor through the server serial port A, using a terminal emulation
program such as Hyperterm on the remote system. The connection can be direct (a
null-modem cable) or through a modem.
Note: The serial port must be connected to either the shared communications (Port
A) port connector (J68) or the dedicated (system management) port
connector (J65) on the system board. See “System board options connectors”
on page 47 for the location of the connectors.
To use the remote terminal functions of the onboard service processor:
1. Establish the connection from the remote computer to the service processor.
Note: The server does NOT have to be running for the remote computer to
connect to the service processor.
2. Press Esc.
3. Log in using the dial-in userid and password defined in the server
Configuration/setup Utility program. The default userid is USERID; the default
password is PASSW0RD (the 6th character is zero).
The service processor presents a menu of actions you can choose:
Selection Meaning
2 - Monitors View the temperature, voltages, fans, or service
3 - Error Logs View the system error log or the service processor error
4 - SP configuration View the service processor configuration
12 Hardware Maintenance Manual: xSeries 330 Type 8675
processor status monitors
log
Selection Meaning
5 - System Services View information about the settings for system services
6 - System Power View settings or turn server power on or off
7 - Boot Restart the server (server power must be on) or the
service processor.
B - Remote Terminal Status View the status of another remote terminal and its
components from this remote terminal.
E - Storage View the number of hard drives installed and their SCSI
IDs
R - Remote SP Access View the service processor information for other servers
that are connected to your server through your server’s
RS-485 ports (ASM bus).
Y - Disconnect current login End the connection for the current userid and password
Z - Start Remote Video Begin redirecting the server video and keyboard
input/output to the remote terminal screen and
keyboard.
4. Enter the number or letter that represents the action that you want. Each
selection gives a further menu, from which you choose the particular element.
For example, to turn the server power on, first enter the number for System
Power, then enter the number for Power On in the resulting menu.
5. When the line 0 -Write or2 - Read appears, press 0 (zero) to send the
command to the service processor, or press 2 to retrieve the requested
information from the service processor.
Notes:
a. If you reboot the service processor, the connection is ended and you will
have to log in again.
b. When you initiate Start Remote Video, the menu goes away. Press Ctrl-R +
Ctrl-E + Ctrl-T to redisplay the menu.
c. From any selection, press Esc to return to the main menu.
Running remote diagnostics
To run diagnostics on the server from a remote terminal, do the following:
1. Make sure the server is turned on and running.
2. Establish the connection from the remote computer to the server (see
“Connecting to the onboard service processor” on page 12) and log in.
3. When the server processor menu appears, enter 7 (boot), then enter the number
for your choice to restart the server, then enter 0 (write the command to the
server).
4. Return to the main menu and immediately enter Z (Start remote video), then
enter 0 (zero). The server monitor contents are displayed on the remote
monitor.
5. When the message F2 for Diagnostics appears, press F2 on the remote
computer keyboard. The diagnostic programs screen appears. Run the
diagnostics you need. See “Diagnostic programs and error messages” on
page 18 for more information about running the diagnostics program.
Important: You cannot run the following tests remotely:
v Keyboard
v Video
v Mouse
v USB
General information 13
v Serial ports
v ASM restart (under System Management)
Also, the following tests require user interaction at the server:
v Diskette
v CDROM/DVD
v CDRW
v Parallel port external loopback
v Ethernet external loopback
v Modem
6. When you have completed the diagnostics tests, exit the diagnostics programs.
To return to the service processor main menu, enter Ctrl-R + Ctrl-E + Ctrl-T.
Special keystrokes
When running the diagnostics programs remotely through a terminal emulation
program, some function keys might not work. Use the following key combinations
for the function keys that do not work.
To transmit: Type:
F1 Ctrl-A
F2 Ctrl-O
F3 Ctrl-L
F5 Ctrl-D
Enter Ctrl-N
Page Up Ctrl-Q
Page Down Ctrl-Z
Considerations when using IBM Remote Supervisor Adapter
To connect a remote terminal, follow the instructions in the documentation that
comes with the IBM Remote Supervisor Adapter.
When using the remote terminal to Redirect Text Console mode, keyboard control
is limited to ASCII characters and arrow keys. You can simulate some special keys
by using certain key combinations. The key combinations consist of a prefix (Ctrl-]
or Ctrl-Z) followed by designated keystrokes:
To transmit: Type:
F1-F9, F10 Prefix followed by 1-9, 0
F11 Prefix followed by F12 Prefix followed by =
Page Up Prefix followed by Ctrl-u
Page Down Prefix followed by Ctrl-d
Alt-F1 Prefix followed by F1
Ctrl-Alt-Del Prefix followed by Ctrl-r
Note: If one prefix does not work, use the other instead.
14 Hardware Maintenance Manual: xSeries 330 Type 8675
Diagnostics
This section provides basic troubleshooting information to help you resolve some
common problems that might occur with the server.
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 16
for more information.
v 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 18 for more information.
v Light Path Diagnostic
The Light Path Diagnostic is used to quickly identify system errors.
© Copyright IBM Corp. 2001 15
POST
When you turn on the server, it performs a series of tests to check the operation of
server components and some of the options installed in the server. This series of
tests is called the power-on self-test or POST.
If POST finishes without detecting any problems, 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
Enter, when prompted, before POST will continue.
2. A single problem might cause several error messages. When this occurs, work
to correct the cause of the first error message. After you correct the cause of the
first error message, the other error messages usually will not occur the next
time you run the test.
POST error messages
The table “POST error codes” on page 121 provides information about the POST
error messages that can appear during startup.
Error logs
The POST error log contains the three most recent error codes and messages that
the system generated during POST. The System Error log contains all messages
issued during POST and all system status messages from the service processor.
You can view the contents of this error log from the Configuration/Setup Utility
program or from the diagnostics programs.
v Start the Configuration/Setup Utility program; then, select Error Logs from the
main menu. See “Starting the Configuration/Setup Utility program” on page 32
for more information.
v Start the diagnostics programs,; select Hardware Info from the top of the
diagnostics programs screen; select System Error Log from the list that appears;
then, follow the instructions on the screen. See “Starting the diagnostic
programs” on page 20 for more information.
Small computer system interface (SCSI) messages
The following table lists actions to take if you receive a SCSI error message.
Note: If the server does not have a hard disk drive, ignore any message that
indicates that the drive is not installed.
You will get these messages only when running the SCSISelect Utility. See “SCSI
error codes” on page 125.
16 Hardware Maintenance Manual: xSeries 330 Type 8675
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.
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.
Identifying problems using status LEDs
If the System Error light in the Information LED Panel on the front of the server is
on, one or more LEDs inside the server 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 48.
Light Path Diagnostics
You can use the Light Path Diagnostics built into your server 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 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 to shut down. See Table 3 on
page 18.
Important: You have up to 12 hours to use the Light Path Diagnostic LED’s after
ac power has been removed from the server. After 12 hours you must power the
server 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 and any peripheral devices.
2. Remove all external cables and power cords from the server; then, remove the
server from the rack and remove the cover. See “Removing the cover” on
page 51 for more info.
Diagnostics 17
3. 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.
4. Replace the cover on the server; then, reinstall the server in the rack and
connect all external cables and power cords.
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 Error occurred on service processor
PCI Error occurred on an adapter in PCI slot 1 or 2, or one of the PCI service
MEM
CPU
VRM
PCI
devices integrated on the system board.
See “Information panel system error LED” on page 115 for appropriate action.
Diagnostic programs and error messages
The server diagnostic programs are stored in upgradable read-only memory (ROM)
on the system board. These programs are the primary method of testing the major
components of the server.
18 Hardware Maintenance Manual: xSeries 330 Type 8675
Sometimes the first error to occur causes additional errors. In this case, the server
displays more than one error message. Always follow the suggested action
instructions for the first error message that appears.
The following sections contain the error codes that might appear in the detailed
test log and summary log when running the diagnostic programs.
The error code format is as follows:
fff-ttt-iii-date-cc-text message
where:
fff is the three-digit function code that indicates the function being
tested when the error occurred. For example, function code 089 is
for the microprocessor.
ttt is the three-digit failure code that indicates the exact test failure
that was encountered.
iii is the three-digit device ID.
date is the date that the diagnostic test was run and the error recorded.
cc is the check digit that is used to verify the validity of the
information.
text message is the diagnostic message that indicates the reason for the problem.
Text messages
The diagnostic text message format is as follows:
Function Name: Result (test specific string)
where:
Function Name
is the name of the function being tested when the error occurred. This
corresponds to the function code (fff) given in the previous list.
Result can be one of the following:
Passed
Failed This result occurs when the diagnostic test discovers an error.
User Aborted
Not Applicable
Aborted
This result occurs when the diagnostic test completes without any
errors.
This result occurs when you stop the diagnostic test before it is
complete.
This result occurs when you specify a diagnostic test for a device
that is not present.
This result occurs when the test could not proceed because of the
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.
Diagnostics 19
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 Esc.
To start the diagnostic programs:
1. Turn on the server and watch the screen.
2. When the message F2 for Diagnostics appears, press F2.
If a power-on password is set, the server prompts you for it. Type the power-on
password, and press Enter.
3. When the Diagnostic Programs screen appears, select either Extended or Basic
from the top of the screen.
4. Select the test you want to run from the list that appears; then, follow the
instructions on the screen.
Notes:
a. If the server stops during testing and you cannot continue, restart the server
and try running the diagnostic programs again.
b. The keyboard and mouse (pointing device) tests assume that a keyboard
and mouse are attached to the server.
c. If you run the diagnostic programs with no mouse attached to the 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.
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 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.
If the hardware checks out OK but the problem persists during normal server
operations, a software error might be the cause. If you suspect a software problem,
refer to the information that comes with the software package.
Viewing the test log
When the tests have completed, you can view the Test Log by selecting Utility
from the top of the screen and then selecting View Test Log.
Notes:
1. You can view the test log only while you are in the diagnostics programs.
When you exit the diagnostics programs, the test log is cleared (saved test logs
are not affected). To save the test log so that you can view it later, click Save
Log on the diagnostic programs screen and specify a location and name for the
saved log file.
20 Hardware Maintenance Manual: xSeries 330 Type 8675
2. To save the test log to a diskette, you must use a diskette that you have
formatted yourself; this function does not work with preformatted diskettes. If
the diskette has sufficient space for the test log, the diskette may contain other
data.
Diagnostics 21
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.
1. Turn off the server 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. Move the jumper from pins 2 and 3 to 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. The system begins the power-on self-test (POST) and BIOS
flash.
7. Select 1 - Update POST/BIOS from the menu that contains various flash
(update) options.
22 Hardware Maintenance Manual: xSeries 330 Type 8675
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 restart your system at this time.
11. Remove the BIOS Flash Diskette from the diskette drive.
12. Turn the server off.
13. Move the jumper on J19 to pins 2 and 3 to return to normal startup mode.
14. 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
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.
v Check for operating system-specific causes for the problem.
v Make sure that the device drivers on the client and server are using the same
protocol.
v Test the Ethernet controller:
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 23
Table 4. Ethernet troubleshooting chart
Ethernet controller problem Suggested Action
The server 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.
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 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 error messages
The integrated Ethernet controller might display messages from the following
device drivers:
v Novell NetWare or IntraNetWare Server ODI
v NDIS Adapter for level 4.0 (Windows NT or Windows 2000)
Notes:
1. Listing these device drivers does not imply that these operating systems are
supported on this server. Refer to http://www.ibm.com/ on the World Wide
Web for the supported operating systems for the server.
2. Although the term ″adapter″ is used in these messages, the messages might
also apply to the integrated Ethernet controller on the system board.
NDIS 4.0 (Windows NT or 2000) driver messages
This section contains the error messages for the NDIS 4.0 drivers. The explanation
and recommended action are included with each message.
24 Hardware Maintenance Manual: xSeries 330 Type 8675
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.
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:
For Windows 2000
1. From the Windows 2000 desktop, click Start→ Settings→Control Panel→Network and Dial-up
connections.
2. Right-click the connection that uses your IBM Ethernet adapter, and click Properties.
3. Click Configure→Advanced.
4. Lower the resource values that apply to the transmit queue.
For Windows NT:
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:
For Windows 2000:
1. From the Windows 2000 desktop, click Start→ Settings→Control Panel→Network and Dial-up
connections.
2. Right-click the connection that uses your IBM Ethernet adapter, and click Properties.
3. Click Configure→Advanced.
4. Lower the resource values that apply to the receive queue.
For Windows NT:
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.
Diagnostics 25
Table 5. NDIS (Windows NT or Windows 2000) driver messages for the Ethernet controller (continued)
Error code (hex) Description
0x0F Explanation: Could not allocate enough memory for other structures. Action:
For Windows 2000:
1. From the Windows 2000 desktop, click Start→ Settings→Control Panel→Network and Dial-up
connections.
2. Right-click the connection that uses your IBM Ethernet adapter, and click Properties.
3. Click Configure→Advanced.
4. Lower the value for the resource named in the message.
For Windows NT:
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.
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
is an invalid configuration. Action: Reconfigure the adapter team by
double-clicking the PROSet icon in the control panel.
02 Error Explanation: Unable to allocate required resources. Action: Free some
memory resources and restart.
03 Error Explanation: Unable to read required registry parameters. Action:
Reconfigure the adapter team by double-clicking the PROSet icon in the
control panel.
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 am nn. Primary adapter is initialized. Action: None.
07 Informational Explanation: Te am nn. Secondary adapter is initialized. Action: None.
08 Informational Explanation: Te am nn. Virtual adapter or Team is initialized. Action:
None.
09 Informational Explanation: Te am nn. Primary adapter is switching over. Action: None.
26 Hardware Maintenance Manual: xSeries 330 Type 8675
Loading...