IBM x330 User Manual
Hardware Maintenance Manual
xSeries 330
IBM
Hardware Maintenance Manual
xSeries 330
IBM
Note: Before using this information and the product it supports, be sure to read the general information under
“Notices” on page 147.
First Edition (September 2000)
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 transa ctions,
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 incorpor ated 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 ma y
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.
xSeries 300
© Copyright International Business Machines Corporation 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Sch edu le Cont ra ct wit h
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
xSeries 330.
Important: This manual is intended for trained se rvicers who are familiar with IBM
PC Server products.
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.
®
© Copyright IBM Corp. 2000 iii
Prenez connaissance de toutes les consignes de type Attention et
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 d i effettuare
qualsiasi operazione.
Online Support
IBM Online Addresses
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a cabo
cualquier operación.
Use the World Wide Web (WWW) to download Diagnostic, BIOS Flash, and Device
Driver files.
File download address is:
http://www.us.pc.ibm.com/files.html
The HMM manuals online address is:
http://www.us.pc.ibm.com/cdt/hmm.html
The IBM PC Company Support Page is:
http://www.us.pc.ibm.com/support/index.html
The IBM PC Company Home Page is:
http://www.pc.ibm.com
iv Hardware Maintenance Manual: xSeries 330
Contents
About this manual . . . . . . . . . . . . . . . . . . . iii
Important safety information . . . . . . . . . . . . . . . . . . . . . . iii
Online Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
IBM Online Addresses . . . . . . . . . . . . . . . . . . . . . . . . . iv
Chapter 1.General checkout . . . . . . . . . . . . 1
Chapter 2.General information . . . . . . . . . . 3
Features and specifications . . . . . . . . . . . . . . . . . . . . . . . . 4
What the xSeries 330 offers . . . . . . . . . . . . . . . . . . . . . . . . 5
Reliability, availability, and serviceability features . . . . 5
Server controls and indicators. . . . . . . . . . . . . . . . . . . . . . 6
Front view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Rear view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Turning on the server . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Turning off the server . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Stand-by mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3.Diagnostics. . . . . . . . . . . . . . . . 11
Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . . . . . 11
POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
POST error messages. . . . . . . . . . . . . . . . . . . . . . . . . . 12
Event/error logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
Novell NetWare or IntraNet Ware server ODI driver
teaming messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
NDIS 4.0 (Windows NT) driver messages . . . . . . . . 22
Power checkout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Replacing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Temperature checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 4.Configurin g th e se rver. . . . . . . 29
Using the Configuration/Setup Utility program. . . . . 29
Starting the Configuration/Setup Utility program 29
Choices available from the Configuration/Setup main
menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Power-on password . . . . . . . . . . . . . . . . . . . . . . . . 34
Administrator password . . . . . . . . . . . . . . . . . . . . 35
Using the SCSISelect utility program. . . . . . . . . . . . . . . 36
Starting the SCSISelect utility program . . . . . . . . . . 36
Choices available from the SCSISelect menu . . . . . 36
Using the Preboot eXecution Environment boot agent
utility program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Starting the PX E boot agent utility program . . . 37
Choices available from the PXE boot agent utility .
38
Chapter 5.Installing options. . . . . . . . . . . 39
Major components of the xSeries 330 server . . . . . . . . . 39
System board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
System board options connectors . . . . . . . . . . . . . . . 40
System board LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
System reliability considerations. . . . . . . . . . . . . . . . 42
Working inside a server with power on . . . . . . . . . . 42
Rack installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Removing the cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Working with adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Adapter considerations . . . . . . . . . . . . . . . . . . . . . . . . 45
Installing an adapter . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Hard disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Preinstallation steps . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Installing or replacing a hard disk drive. . . . . . . . . . 49
Hot-swap disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Preinstallation steps. . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Installing hot-swap disk drives . . . . . . . . . . . . . . . . . 50
Replacing a drive in a hot-swap bay . . . . . . . . . . 51
Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Installing memory modules . . . . . . . . . . . . . . . . . . . . 53
Microprocessor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Installing the microprocessor. . . . . . . . . . . . . . . . . . . 56
Removing a microprocessor. . . . . . . . . . . . . . . . . . . . 57
Fan assembly replacement . . . . . . . . . . . . . . . . . . . . . . . . 59
Installing the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
I/O connector locations and ports . . . . . . . . . . . . . . . . . 61
Input/Output ports . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Serial port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Universal Serial Bus ports . . . . . . . . . . . . . . . . . . . 63
Cable Chaining Technology (C2T) ports. . . . . . . 64
C2T chaining cable . . . . . . . . . . . . . . . . . . . . . . . . . 65
C2T breakout cable . . . . . . . . . . . . . . . . . . . . . . . . . 65
Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Advanced System Management ports. . . . . . . . . 70
Working with cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Cabling the RS-485 ports. . . . . . . . . . . . . . . . . . . . . . . 71
Connecting the ASM bus. . . . . . . . . . . . . . . . . . . . 72
Connecting the servers with a C2T chain. . . . . . . . . 72
Testing the C2T chain . . . . . . . . . . . . . . . . . . . . . . . 74
Cable management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 6.FRU information (service only)77
Diskette/CD-ROM drives . . . . . . . . . . . . . . . . . . . . . . . . 77
Diskette/CD-ROM drive bracket . . . . . . . . . . . . . . . . . . 78
Hard disk drive backplane. . . . . . . . . . . . . . . . . . . . . . . . 79
Power supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
PCI riser card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
System board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 7.Sy mptom-to-FRU ind ex . . . . . . 8 3
Beep symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
No Beep symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Information panel system error LED . . . . . . . . . . . . . . . 85
Diagnostic error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
POST error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
SCSI error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Temperature error messages . . . . . . . . . . . . . . . . . . . . . . 95
Fan error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
© Copyright IBM Corp. 2000 v
System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Voltage related system shutdown . . . . . . . . . . . . . . . 96
Temperature related system shutdown . . . . . . . . . . 97
DASD checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Bus fault messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Undetermined problems . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 8.Parts listing. . . . . . . . . . . . . . . 101
System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Keyboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Chapter 9.Related service information . 107
Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
General safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Electrical safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Safety inspection guide . . . . . . . . . . . . . . . . . . . . . . . 109
Handling electrostatic discharge-sensitive devices 110
Grounding requirements. . . . . . . . . . . . . . . . . . . . . . 111
Safety notices (multi-lingual translations) . . . . . . . 111
Send us your comments! . . . . . . . . . . . . . . . . . . . . . . . . 146
Problem determination tips . . . . . . . . . . . . . . . . . . . . . . 147
Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
vi Hardware Maintenance Manual: xSeries 330
Chapter 1. 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 the server: the system board, Ethernet controller, video controller,
RAM, keyboard, mouse (pointing device), diskette drive, serial ports, and hard
drives. You can also use them to test some external devices. See “Diagnostic
programs and error messages” on page 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:
• The customer identifies the system as part of a cluster.
• One or more external storage units are attached to the system and at least one of
the attached storage units is additionally attached to another system or
unidentifiable source.
• One or more systems are located near the failing system.
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 107.
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 mult iple 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 90.
5. For intermittent problems, check the error log; see “Event/error logs” on page 12.
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:
• Power-off the computer and all external devic es.
• Check all cables and power cords.
• Set all display controls to the middle position.
• Power-on all external devices.
© Copyright IBM Corp. 2000 1
• Power-on the computer.
• If the computer hangs and no error is displayed, go to “Undetermined
problems” on page 98.
• 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 90.
• Check the information LED panel System Error LED; if on, see “Information
panel system error LED” on page 85.
• Check the System Error Log. If an error was recorded by the system, see
“Chapter 7. Symptom-to-FRU index,” on page 83.
• Start the Diagnostic Programs. See “Diagnostic programs and error
messages” on page 15.
• 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“Chapter 7. Symptom-to-FRU index,” on page 83.
YES.Run the Diagnostic Programs. If necessary, refer to “Starting the diagnostic
programs” on page 16.
If you receive an error, go to“Chapter 7. Symptom-to-FRU index,” on p age 83.
If the diagnostics completed successfully a nd you still suspect a problem, see
“Undetermined problems” on page 98.
2 Hardware Maintenance Manual: xSeries 330
Chapter 2. General information
The IBM
®
xSeries 330 server is a one U-high
1
rack-model server for highvolume network transaction processing. This high-performance, symmetric
multiprocessing (SMP) server is ideally suited for netw orking environments that
require superior microprocessor performance, efficient memory management,
flexibility, and reliable data storage.
The xSeries 330 server comes with a three-year limited warranty and IBM Server Start
Up Support. If you have access to the World Wide Web, you can obtain up-to-date
information about your xSeries 330 model and other IBM server products at the
following World Wide Web address: 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. 2000 3
Features and specifications
The following table provides a summary of the features and specifications for the
xSeries 330 server.
Table 1. Features and Specification s.
Microprocessor:
• Intel
• 2 56 KB Level-2 cache
• Supports up to two
Memory:
• Standard: 256 MB
• Maximum: 4 GB
• Type: 133 MHz, ECC, SDRAM,
• Slots: 4 dual inline
Drives standard:
• Diskette: 1.44 MB
• CD-ROM: 24X IDE
Expansion bays:
• Two 3.5-inch slim high bays for
PCI expansion slots:
• Two 33 MHz/64-bit
Power supply:
One 200 watt (115-230 Vac)
Video:
• S3 Savage4 PRO
• Compatible with SVGA
• 8 MB SDRAM video memory
®
Pentium® III
microprocessor with MMX™
technology and SIMD
extensions
microprocessors
Registered DIMMs
LVD SCSI hard disk drives
Graphics/Video Accelerator
(integrated on system board)
Size
• Height 43.69 mm (1.72")
• Depth: 653.29 mm (25.72")
• Width: 439.93 mm (17.32")
• Weight: approximately 12.7 kg
(28lb) when fully configured
Integrated functions:
• Advanced System Management
processor
• One Ultra160 SCSI controller
• Two 10BASE-T/100BASE-TX
Intel Ethernet controllers
• Two Universal Serial Bus (USB)
ports
• Two RS-485 Advanced System
Management processor ports
(one In, one Out)
• One serial port
• Two Cable Chaining Techn ology
ports (IN, OUT)
Acoustical noise emissions:
• Sound power, idling: 6.1 bel
maximum
• Sound power, operating: 6.2 bel
maximum
Environment:
• Air temperature:
— Server on: 10º to 35º C (50.0º to
95.0º F). Altitude: 0 to 914 m
(2998.7 ft.)
— Server on: 10º to 32º C (50.0º to
89.6º F). Altitude: 914 m
(2998.7 ft.) to 2133 m (6998.0 ft.)
— Server off: 10º to 43º C (50.0º to
109.4º F). Maximum altitude:
2133 m (6998.0 ft.)
• Humidity:
— Server on: 8% to 80%
— Server off: 8% to 80%
Heat output:
Approximate heat output in British
Thermal Units (BTU) per hour
• Minimum configuration: 273 BTU
(80 watts)
• Ma ximum configuration: 751 BTU
(220 watts)
Electrical input:
• Sine-wave input (50-60 Hz)
required
• Input voltage low range:
— Minimum: 100 V ac
— Maximum: 127 V ac
• Input voltage high range:
— Minimum: 200 V ac
— Maximum: 240 V ac
• Input kilovolt-amperes (kVA)
approximately:
— Minimum: 0.08 kVA
— Maximum: 0.22 kVA
What the xSeries 330 offers
The unique design of this server takes advantage of ad vancements in symmetric
multiprocessing (SMP), data storage, and memory management. The server
combines:
4 Hardware Maintenance Manual: xSeries 330
• 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.
• 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, synchronousdynamic-random access memory (SDRAM) dual inline memory modules
(DIMMs).
• 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.
• Integrated network environment support
The server comes with two Ethernet controllers on the system board. Each
Ethernet controller has an interface for co nnecting 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).
• 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 failu re with mi nimal
inconvenience.
The following is an abbreviated list of the RAS features that your server supports.
• Menu-driven setup, system configuration, RAID configuration, and diagnostic
programs
• Power-on self-test (POST)
• Integrated Advanced System Management Processor
• Predictive Failure Alerts (PFA)
• Remote system problem-analysis support
• Power and temperature monitoring
• Hot-swap drive bays
Chapter 2. General information 5
• Error codes and messages
• System error logging
• Upgradable BIOS, diagno stics, and Advanced System Management Processor
code
• Automatic restart after a power failure
• Parity checking on the PCI buses
• CRC checking on the SCSI buses
• Error checking and correcting (ECC) memory
• Redundant Ethernet capabilities
• Light Path Diagnostics ™ o n the system board
• Vital Product Data (VPD) on system boa rd, 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). Yo u mi ght n eed 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.
Hard disk drive status lig ht: Each of the hot-s wap drives has a har d disk driv e status
light. When this amber LED is on continuously , the drive has failed. This status light
is active only with a ServeRAID adapt er installed in the server.
6 Hardware Maintenance Manual: xSeries 330
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
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.
Chapter 2. General information 7
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.
• 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 20 seconds before pressing the Power control button.
During this time, the system-management processor is initializing and the
Power control button does not respond.
• If the server is turned on and a power failure occurs, the server will start
automatically when power is restored.
• The 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.
2
1
Turning off the server
Turning off the server refers to the act of disconnecting the server from the power
source.
8 Hardware Maintenance Manual: xSeries 330
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 shutdown 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.
Chapter 2. General information 9
10 Hardware Maintenance Manual: xSeries 330
Chapter 3. 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:
• POST beep codes, error messages, and error logs
The power-on self-test (POST) generates be ep codes and messages to indi cate
successful test completion or the detection of a problem. See “POST” on page 12
for more information.
• Diagnostic programs and error messages
The server diagnostic programs are stored in upgradable read-only memory
(ROM) on the system board. These programs are the primary method of testing
the major components of your server. See “Diagnostic programs and error
messages” on page 15 for more information.
• Light Path Diagnostic
The Light Path Diagnostic is used to quickly identify system errors.
© Copyright IBM Corp. 2000 11
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. Thi s 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 err or m essage appea rs
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 90 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 does not have a hard disk drive, ignore any message that indicates
that the drive is not installed.
Y o u will get these messages only when running the SCSISelect Utility. See “SCSI err or
codes” on page 95.
12 Hardware Maintenance Manual: xSeries 330
Table 2. SCSI messages.
SCSI Messages Description
All One or more of the following might be causing the pro blem.
• A failing SCSI device (adapter, drive, controller)
• An improper SCSI configuration
• Duplicate SCSI IDs in the same SCSI chain
• An improperly installed SCSI terminator
• A defective SCSI terminator
• An improperly installed cable
• A defective cable
Action:
Verify that:
• The external SCSI devices are turned on. External SCSI devices must
be turned on before the server.
• The cables for all external SCSI devices are connected correctly.
• The last device in each SCSI chain is terminated properly.
• 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 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 41.
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 Li ght 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-illumi na ted
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 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. 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.
Chapter 3. Diagnost ics 13
To view the LEDs on the system board:
1. Turn off the server and any peripheral devices.
2. Remove the cables.
3. Remove the server from the rack and place it on a flat, non-conductive surface.
4. Remove the server cover (see “Removing the cover” on page 44).
Note: Refer to “Working inside a server with power on” on page 42 for
instructions and precautions for working in the server 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 o f tw o 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 th e system
board. See Table 3 for information on identifying p roblems 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 SP bus
PCI Error occurred on an adapter in PCI slot 1 or 2, or one of the PCI service
devices integrated on the system board.
MEM
CPU
VRM
PCI
See “Information panel syste m error LED” on page 85 for appropriate action.
14 Hardware Maintenance Manual: xSeries 330
Diagnostic pr ogr ams 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.
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 appea r in the detailed test
log and summary log when runnin g 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 This result occurs when the diagnostic test completes without any
Failed This result occurs when the diagnostic test discovers an error.
User Aborted
Not Applicable
Aborted This result occurs when the test could not proceed because of the
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.
system configuration.
Chapter 3. Diagnost ics 15
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 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.
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 se rver stops during testing and you cannot continue, restart the server
and try running the diagnostic programs aga in.
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 functio n 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 hub test
only if there are no USB devices attached.
e. You can view server configuration information (such as system configuration,
memory contents, interrupt request (IRQ) use, direct memory access (DMA)
use, device drivers, and so on) by selecting Hardware Info from the top of the
screen.
When the tests have completed, you can view the Test Log by selecting Utility from
the top of the screen.
If the hardware checks out OK but the problem persists during normal server
operations, a software error might be the cause. If you suspect a software problem,
refer to the information that comes with the software package.
Viewing the test log
The test log will not contain any info rmation until after the diagnostic program has
run.
Note: If you already are running the diagnostic programs, begin with step 3 on page
17.
To view the test log:
16 Hardware Maintenance Manual: xSeries 330
1. Turn on the server and watch the screen.
If the server is on, shut down your operating system and restart the server:
2. When the message F2 for Diagnostics appears, press F2.
If a power-on password is set, the server prompts you for it. Type in the
appropriate password; then, press Enter.
3. Wh en the Diagnostic Programs screen app ears, select Utility from the top of the
screen.
4. Select View Test Log from the list that appears; then, follow the instructions on
the screen.
The system maintains the test-log data while the server is powered on. When you
turn off the power to the server, the test log is cleared.
Chapter 3. Diagnost ics 17
Recovering BIOS
If the BIOS has become corrupted, such as fro m a power failur e 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:
1. Turn off the server and peripheral devices and disconnect all external cables and
2. Locate the BIOS code page jumper (J19) on the system board.
• Use the ServerGuide program to make a BIOS flash diskette.
• Download a BIOS flash diskette from the World Wide Web. Go to http:
//www.pc.ibm.com/support/, select IBM Server Support, and make the
selections for your server.
• Contact your IBM service representative.
power cords; then, remove the cover.
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. The system begins the power-on self-test (POST) and BIOS
flash.
7. Select 1 - Update POST/BIOS from t h e m enu that contains v a r io us flash (update)
options.
18 Hardware Maintenance Manual: xSeries 330
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 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:
• 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: T o determine whether a hub has an X port, check the port label. If the label
contains an X, the hub has an X port.
• Determine if the hub supports auto-negotiation. If n ot, try co nfiguring the
integrated Ethernet controller manually to match the speed and duplex mode of
the hub.
• Check the LAN activity light on the front of the server. The LAN activity light
illuminates when the Ethernet controller sends or receives data over the Ethernet
Network. If the LAN activity light is off, make sure that the hub and network are
operating and that the correct device drivers are loaded.
• Make sure that you are using the correct device drivers, supplied with the server.
• Check for operating system-specific causes for the problem.
• Make sure that the device drivers on the client and server are using the same
protocol.
• Test the Ethernet controller:
How you test the Ethernet controller depends on which operating system you are
using (see the Ethernet controller device driver README file).
Ethernet controller troubleshooting chart
You can use the following troubleshooting chart to find solutions to 10/100 Mbps
Ethernet controller problems that have definite symptoms.
Chapter 3. Diagnost ics 19
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 PCI BIOS interrupt settings are incorrect.
Check the following:
• Determine if the interrupt (IRQ) setting assigned to the Ethernet controller is also
assigned to another device in the Configuration/Setup Utility program.
Although interrupt sharing is allowed for PCI devices, some devices do not
function well when they share an interrupt with a dissimilar PCI device. 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.
• Make sure that you are using the most recent device driver available from the
World Wide Web.
• Run the network diagnostic program.
• Make sure that you are using Category 5 cabling when operating the server at 100
Mbps.
• Make sure that the cables do not run close to noise-inducing sources like
fluorescent ligh ts.
Check the following:
• Make sure that the cable is connected to the Ethernet controller.
• Make sure that your PCI system BIOS is current.
• Reseat the adapter.
• Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also
assigned to another device in the Configuration/Setup Utility program.
Although interrupt sharing is allowed for PCI devices, some devices do not
function well when they share an interrupt with a dissimilar PCI device. Try
changing the IRQ assigned to the Ethernet adapter or the other device.
The Ethernet controller
stopped working without
apparent cause.
Check the following:
• Run diagnostics for the Ethernet controller.
• Try a differ ent connector on the hub.
• Reinstall the device drivers. Refer to your operating-system documentation and to
the ServerGuide information.
Ethernet controller messages
The integrated Ethernet controller might display messages f rom the following device
drivers:
• Novell™ NetWare™ or IntraNetWare Server ODI
• NDIS Adapter for level 4.0 (Windows NT)
• SCO™ UNIX LLI
20 Hardware Maintenance Manual: xSeries 330
Novell NetWare or IntraNetWare server ODI driver
teaming messages
This section provides explanations of the error messages for the Novell NetWare or
IntraNetWare server ODI driver, and suggested actions to resolve each problem.
Table 5. NetWare driver messages for the Ethernet controller.
Message Description
Couldn’t allocate r eso u rces Explanation: An unknown error has occurred when trying to allocate needed
resources for the AFT Module. Action:
• Check the server configuration. If the problem persists, contact your
network supplier.
• Verify that the Ethernet controller is enabled. If the Ethernet controller is
enabled, run the diagnostic prog ra ms.
AF T group for primary adapter in slot
nnn already exists.
Error locating DCT addresses in
internal table. Make sure that you
have loaded LAN drivers after
loading AFT.NLM.
Explanation: An attempt was made to rebind an adapter already in an AFT
group. Action: Check the AFT slot numbers for existing AFT teams. If the
problem persists, contact your network supplier.
Explanation: The bind command was entered pr ior to loading the device
driver. The device driver must be loaded after loading AFT.NLM but before
any bind command can be issued. Action: Load the driver for the supported
adapter and try loading t he AFT module again. If the problem persists, cont act
your network supplier.
Insufficient number of arguments
specified.
Duplicate slot numbers detected. Explanation: An attempt has been made to bind the same slot number more
’Xxx’ is not supported for AFT team. Explanation: A bind command has been issued for adapters not supported by
Primary and Secondary adapters do
not match. AFT group is not created.
Requested number of Secondary
cards are not found.
Failed to create AFT group. Make
sure that the drivers for supported
adapters are loaded, primary adapter
is bound to protocols, and secondary
adapter is not bound to any protocols.
Error identifying s lot num bers fo r the
specified board names.
Explanation: The appropriate or expected number of parameters was not
entered in a command. Action: Check the parameters required for the given
command. If the problem persists, contact your network supplier.
than once. Action: Check the slot numbers entered during the bind. Adapter
slot numbers must be valid and unique. If the problem persists, contact your
network supplier.
AFT.NLM. Action: Make sure that you attempt to bind only adapters
supported by AFT.NLM.
Explanation: A bind command was entered for an adapter team that is a
combination of server and client adapters. An AFT team must be a grouping of
the same classification of adapter. Action: Verify that all the adapters boun d in
a team are of the same classification.
Explanation: The number of adapters specified in the bind command could
not be located. Action: Verify the numbers and slot locations of the adapters to
be bound. If the problem persists, contact your network supplier.
Explanation: Binding of protocol failed. Protocol is either not bound to any
adapter or is bou nd to m ore than o ne adapt er in th e gr oup. Action: Ensur e t hat
the protocol is bound to only adapter in an AFT team.
Explanation: The mapping between the bo ard name entered and the slot
number for an adapter could not be estab lished. Actio n: Check the boar d name
for the adapter before issuing the bind command. If the problem persists,
contact your network supplier.
Chapter 3. Diagnost ics 21
Table 5. NetWare driver messages for the Ethernet controller.
Can’t unbind specified slot from AFT
group. Make sure that the slot you
specified is for the primary ada pter in
an AFT group.
LAN adapter at slot nnnn (Port 0xaa)
failed to reset. Check the state of the
adapter.
AFT is not supported on this version
of NetWare(TM).
Failed to allocate resources tags. Explanation: An unknown error has occurred when trying to allocate needed
Please unload all LAN drivers before
unloading AFT.NLM.
Explanation: The number entered in the unbind command was not the
primary adapter in an AFT group. Action: Reissue the unbind command and
specify the slot number for the primary adapter.
Explanation: The adapter that you specified could not be initialized. Action:
1. Load the driver for the supported adapter.
2. Check that the adapter is seated properly in the slot and try loading the
AFT module again.
If the problem persists, contact your network supplier.
Explanation: The NetWare on your server is not a version supported by AFT.
Action: Load and bind AFT only on supported versions of NetWare (current ly
version 4.11 and above).
resources for the AFT module. Action: Check Server Configuration. If the
problem persists, contact your network supplier.
Explanation: An attempt was made to unload the AFT.NLM module before
unloading the adapter driver. Action: Unload the adapter driver before
unloading the AFT module.
NDIS 4.0 (Windows NT) driver messages
This section contains the error messages for the NDIS 4.0 drivers. The explan ation and
recommended action are included with each message.
Table 6. 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:
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.
22 Hardware Maintenance Manual: xSeries 330
Loading...