IBM Netfinity 6000R Hardware Maintenance Manual

IBM Netfinity Servers

IBM Netfinity 6000R - Type 8682

Models 1RY, 2RY

Hardware Maintenance Manual

March 2000

IBM Netfinity Servers

IBM Netfinity 6000R - Type 8682

Models 1RY, 2RY

Hardware Maintenance Manual

March 2000

IBM

Note: Before using this information and the product it supports, be sure to read the general information under “Notices” on page 236.

First Edition (March 2000)

INTERNATIONAL BUSINESS MACHINES CORPORA-

TION 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 FIT-

NESS 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.

Netfinity 6000R

© COPYRIGHT INTERNATIONAL BUSINESS MACHINES

CORPORATION, 2000. All rights reserved.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM

Corp.

IBM

About this manual

This manual contains diagnostic information, a Symptom-to-

FRU index, service information, error codes, error messages, and configuration information for the Netfinity 6000R

– Type 8682.

Important: This manual is intended for trained servicers 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.

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.

v

Accertarsi di leggere tutti gli avvisi di attenzione e di pericolo prima di effettuare qualsiasi operazione.

Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a cabo cualquier operación.

Online support

Use the World Wide Web (WWW) to download Diagnostic,

BIOS Fl;ash, and Device Driver files.

File download address is:

http://www.us.pc.ibm.com/files.html

IBM online addresses

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

vi

Netfinity 6000R Type 8682 Models 1RY, 2RY

Contents

About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

General checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Features and specifications. . . . . . . . . . . . . . . . . . . . . . . . . 3

Server features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Reliability, availability, and serviceability . . . . . . . . . . . . . . . 7

Start the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Information LED panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . . . . . . 13

POST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

POST beep codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

POST error messages . . . . . . . . . . . . . . . . . . . . . . . . . 14

Event/error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Small computer system interface messages. . . . . . . . . . . 14

ServerGuide error symptoms . . . . . . . . . . . . . . . . . . . . . . 14

Diagnostic programs and error messages . . . . . . . . . . . . 16

Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Starting the diagnostic programs . . . . . . . . . . . . . . . . . 17

Viewing the test log . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Diagnostic error message tables . . . . . . . . . . . . . . . . . 18

Light path diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Diagnostic panel LEDs 20

Light path diagnostics 22

Power checkout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Recovering BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Replacing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Temperature checkout. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Diagnosing errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Troubleshooting the Ethernet controller. . . . . . . . . . . . 28

Network connection problems 28

Ethernet controller troubleshooting chart 29

Ethernet controller messages . . . . . . . . . . . . . . . . . . . 31

Novell NetWare or IntraNetWare server ODI driver messages 31

Network driver interface specification 2.01 (OS/2) driver messages 35

NDIS 4.0 (Windows NT) driver messages 37

UNIX messages 38

Configuring the server . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Using the Configuration/Setup Utility program . . . . . . . . . 43

Starting the Configuration/Setup Utility program . . . . . 43

Choices available from the Configuration/Setup main menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Using passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Power-on password 48

Administrator password 50

Using the SCSISelect utility program . . . . . . . . . . . . . . . . 50

Starting the SCSISelect utility program . . . . . . . . . . . . 51

Choices available from the SCSISelect menu . . . . . . 51

Installing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Expanded view of the Netfinity 6000R . . . . . . . . . . . . . . . 53

Component locations . . . . . . . . . . . . . . . . . . . . . . . . . . 54

System board component locations 54

System board LED locations 59

Diagnostic panel LEDs 60

vii

Memory board component locations 62

Advanced System Management Interconnect board component locations . . . . . . . . . . . . . . . . . . . . . . . . .63

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

System reliability considerations . . . . . . . . . . . . . . . . .64

Working inside the server with the power on . . . . . . . .64

Handling static-sensitive devices . . . . . . . . . . . . . . . . .65

Removing the server top cover and bezel . . . . . . . . . . . . .67

Working with adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Installing a hot-plug adapter . . . . . . . . . . . . . . . . . . . . .69

Cabling example for the ServeRAID adapter . . . . . . . .71

Installing internal drives . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Internal drive bays . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Hard disk drive component locations 75

Installing a hot-swap hard disk drive . . . . . . . . . . . . . .76

Installing memory-module kits . . . . . . . . . . . . . . . . . . .78

Installing a microprocessor kit . . . . . . . . . . . . . . . . . . . . .81

Changing jumper positions . . . . . . . . . . . . . . . . . . . . . .85

Three-pin jumper blocks 85

Installing a hot-swap power supply . . . . . . . . . . . . . . . . . .85

Installing a Netfinity 3-Pack Ultra160 Hot-Swap Expansion

Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Replacing a hot-swap fan . . . . . . . . . . . . . . . . . . . . . . . . .90

Completing the installation . . . . . . . . . . . . . . . . . . . . . . . . .91

Installing the server top cover and bezel . . . . . . . . . . .91

Updating the server configuration. . . . . . . . . . . . . . . . .92

Connecting external options . . . . . . . . . . . . . . . . . . . . . . .92

Input/Output ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Parallel port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Viewing or changing the parallel-port assignments 94

Parallel port connector 94

Video port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Keyboard port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Auxiliary-device (pointing device) port . . . . . . . . . . . . .96

Ultra160 SCSI ports . . . . . . . . . . . . . . . . . . . . . . . . . . .97

SCSI cabling requirements 97

Setting SCSI IDs 97

SCSI connector pin-number assignments 98

Serial ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Viewing or changing the serial-port assignments 99

Serial-port connectors 99

Universal Serial Bus ports . . . . . . . . . . . . . . . . . . . . . 100

USB cables and hubs 100

USB-port connectors 100

Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Configuring the Ethernet controller 101

Failover for redundant Ethernet 101

Ethernet port connector 105

Advanced System Management ports . . . . . . . . . . . .105

Cabling the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Netfinity Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Managing your IBM Netfinity server with Netfinity Manager .

109

Netfinity Manager documentation . . . . . . . . . . . . . . . . . . 110

Netfinity Manager system requirements . . . . . . . . . . . . . 110

Netfinity Manager for OS/2 system requirements. . . . 110

Netfinity Manager for Windows 95 and Windows 98 system requirements . . . . . . . . . . . . . . . . . . . . . . . . 111

Netfinity Manager for Windows NT system requirements.

112

Starting the Netfinity Manager installation program . . . . . 112

Netfinity Manager database support . . . . . . . . . . . . . . . . 119

DB2 database support . . . . . . . . . . . . . . . . . . . . . . . .120

System requirements 120

Installing and configuring the database 120

Activating the database 121

Granting and revoking database privileges 122

viii


Deleting the database 123

Lotus Notes database support . . . . . . . . . . . . . . . . . . 124


Installing the database 124

Browsing the Netfinity Manager Lotus Notes database

125

ODBC database support . . . . . . . . . . . . . . . . . . . . . . 126


ODBC database configuration 127

Creating the Netfinity Manager tables 127

Supported and certified databases 129

Starting Netfinity Manager. . . . . . . . . . . . . . . . . . . . . . . . 132

Netfinity Manager Service Manager. . . . . . . . . . . . . . 132

Netfinity Manager service descriptions . . . . . . . . . . . 133

Advanced System Management 134

Alert Manager 134

Alert on LAN configuration 134

Capacity Management 134

Cluster Manager 134

Critical File Monitor 135

DMI Browser 135

ECC Memory Setup 135

Event Scheduler 135

File Transfer 135

Power-On Error Detect 135

Predictive Failure Analysis 135

Process Manager 135

RAID Manager 135

Remote Session 136

Remote System Manager 136

Remote Workstation Control 136

Screen View 136

Security Manager 136

Serial Connection Control 136

Service Configuration Manager 137

Software Inventory 137

System Diagnostics Manager 137

System Information Tool 137

System Monitor 137

System Partition Access 137

System Profile 138

Update Connector Manager 138

Web Manager Configuration 138

Delaying Netfinity Manager startup on OS/2 systems 138

Getting more information about Netfinity Manager . . . . . 139

Installation options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Automated installation . . . . . . . . . . . . . . . . . . . . . . . . 141

Customized installation . . . . . . . . . . . . . . . . . . . . . . . 142

FRU information (service only) . . . . . . . . . . . . . . . . . . 145

LED switch card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Four-fan housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Dual fan mount assembly with cable. . . . . . . . . . . . . . . . 147

Service processor card assembly . . . . . . . . . . . . . . . . . . 148

PCI switch card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Power backplane assembly. . . . . . . . . . . . . . . . . . . . . . . 150

System board assembly with backerplate . . . . . . . . . . . . 151

Symptom-to-FRU index . . . . . . . . . . . . . . . . . . . . . . . . 153

Beep symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

No beep symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Diagnostic panel error LEDs . . . . . . . . . . . . . . . . . . . . . . 157

Diagnostic error codes . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Power supply LED errors . . . . . . . . . . . . . . . . . . . . . . . . 170

POST error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

ServeRAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

I2C bus fault messages. . . . . . . . . . . . . . . . . . . . . . . . . . 180

ix

SCSI error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Temperature error messages . . . . . . . . . . . . . . . . . . . . . .182

Fan error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Power error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 183

System shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Voltage related system shutdown. . . . . . . . . . . . . . . . 185

Temperature related system shutdown. . . . . . . . . . . . 185

DASD checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

CPU checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

Undetermined problems. . . . . . . . . . . . . . . . . . . . . . . . . .186

Parts listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Related service information . . . . . . . . . . . . . . . . . . . . . 195

Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

General safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Electrical safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Safety inspection guide . . . . . . . . . . . . . . . . . . . . . . . 198

Handling electrostatic discharge-sensitive devices . . 199

Grounding requirements. . . . . . . . . . . . . . . . . . . . . . . 200

Safety notices (multi-lingual translations) . . . . . . . . . . 200

Send us your comments! . . . . . . . . . . . . . . . . . . . . . . . . . 235

Problem determination tips . . . . . . . . . . . . . . . . . . . . . . . 236

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

x


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, hard drives, and parallel port.

You can also use them to test some external devices. See

“Diagnostic programs and error messages” on page 16.

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. 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.

2. If multiple error codes are displayed, diagnose the first error code displayed.

3. If the computer hangs with a POST error, go to the

“Symptom-to-FRU index” on page 153.

4. If the computer hangs and no error is displayed, go to

“Undetermined problems” on page 186.

5. Power supply problems, see “Symptom-to-FRU index” on page 153.

6. Safety information, see “Safety information” on page

196.

1

7. For intermittent problems, check the error log; see

“POST error messages” on page 14.

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 devices.

• Check all cables and power cords.

• Set all display controls to the middle position.

• Power-on all external devices.

• Power-on the computer.

• Record any POST error messages displayed on the screen. If an error is displayed, look up the

first error in the “POST error codes” on page 171.

• Check the information LED panel System Error

LED; if on, see “Diagnostic panel error LEDs” on page 157.

• Check the System Error Log. If an error was

recorded by the system, see “Symptom-to-FRU index” on page 153.

•

Start the Diagnostic Programs. See “Diagnostic programs and error messages” on page 16.

• 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 153.

YES. Run the Diagnostic Programs. If necessary, refer to

“Diagnostic programs and error messages” on page 16.

If you receive an error, go to “Symptom-to-FRU index” on page 153.

If the diagnostics completed successfully and you still sus-

pect a problem, see “Undetermined problems” on page 186.

2


General information

The IBM® Netfinity® 6000R server is a high-performance server with the capability of microprocessor upgrade to a symmetric multiprocessing (SMP) server. It is ideally suited for networking environments that require superior microprocessor performance, efficient memory management, flexibility, and large amounts of reliable data storage.

Performance, ease of use, reliability, and expansion capabilities were key considerations during the design of the server.

These design features make it possible for you to customize the system hardware to meet your needs today, while providing flexible expansion capabilities for the future.

The IBM 6000R server comes with a three-year limited warranty and 90-Day IBM Start Up Support. If you have access to the World Wide Web, you can obtain up-to-date information about the server model and other IBM server products at the following World Wide Web address: http://www.ibm.com/pc/us/netfinity/

Features and specifications

The following provides a summary of the features and specifications for the Netfinity 6000R server.

•

Microprocessor:

— Intel® Pentium® III Xeon™

— 32 KB of level-1 cache

— 1 MB or 2 MB Level-2 cache depending upon model

— 100 MHz front-side bus (FSB)

— Supports up to four microprocessors

•

Memory:

— Maximum: 16GB

— Type: ECC, SDRAM, Registered DIMMs

— 16 slots, 4-way interleaved

•

Drives standard:

— Diskette: 1.44 MB

— CD-ROM: 40X IDE

•

Expansion bays:

Hot-swap drives: Three standard slim-high, three optional slim-high

•

Active™ PCI expansion slots:

— One 33 MHz/32-bit

— Three 66 MHz/64-bit

— Two 33 MHz/64-bit

•

Hot-swap power supplies:

270 W (115-230 V ac)

— Minimum: One

— Maximum: Three

•

Redundant cooling:

— Six hot-swap fans

3

•

Video:

— S3 video controller

— Compatible with SVGA and VGA

— 8 MB video memory

•

Size (4 U)

— Height: 178 mm (7 in.) (4 U)

— Depth: 711.2 mm (28 in.)

— Width: 482.6 mm (19 in.)

— Weight: 34.9 kg (77 lb.) to 50.4 kg (111 lb.) depending upon configuration

•

Integrated functions:

— Netfinity Advanced System Management processor with Light Path diagnostics

— Dual channel Ultra160 SCSI controller (one internal and one external channel) (non-RAID)

— One 10BASE-T/100BASE-TX AMD Ethernet controller

— Two serial ports

— One parallel port

— Two universal serial bus ports

— Keyboard port

— Mouse port

— Video port

•

Acoustical noise emissions:

— Sound power, idling: 6.3 bel maximum

— Sound power, operating: 6.3 bel maximum

— Sound pressure, operating: 48 dBa maximum

•

Environment:

— Air temperature:

– Server on: 10º to 35º C (50º to 95º F). Altitude: 0 to 914 m (3000 ft.)

– Server on: 10º to 32º C (50º to 89.6º F). Altitude: 914 m (3000 ft.) to 2133 m (7000 ft.)

– Server off: 10º to 43º C (50º to 110º F). Maximum altitude: 2133 m (7000 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:461 BTU (0.14 kilowatts per hour)

— Maximum configuration: 1796 BTU (0.53 kilowatts per hour)

•

Electrical input:

— Sine-wave input (50-60 Hz) required

— Input voltage low range:

– Minimum: 90 V ac

– Maximum: 137 V ac

— Input voltage high range:

– Minimum: 180 V ac

– Maximum: 265 V ac

4


— Input kilovolt-amperes (kVA) approximately:

– Minimum: 0.08 kVA

– Maximum: 0.52 kVA

Server features

The unique design of the server takes advantage of advancements in symmetric multiprocessing (SMP), data storage, and memory management. The server combines:

• Impressive performance using an innovative approach to SMP

The server supports up to four Pentium III Xeon processors. The server comes with at least one processor installed; you can install additional processors to enhance performance and provide SMP capability.

• Large data-storage and hot-swap capabilities

All models of the server support up to three standard and three optional 26 mm (1-inch) slim-high 3.5-inch hot-swap hard disk drives in the hot-swap bays. This

hot-swap

feature enables you to remove and replace hard disk drives without turning off the server.

• Active™ PCI (hot-plug) adapter capabilities

The server has six

hot-plug

slots for PCI adapters.

With operating system support, you can replace failing hot-plug PCI adapters without turning off the server. If the

hot-add

feature is supported by the operating system and the PCI adapter, you can also add PCI adapters in these slots without turning off the server.

• Redundant cooling and power capabilities

The redundant cooling and hot-swap capabilities of the fans in the server enable continued operation if one of the fans fails. You can also replace a failing fan without turning off the server.

The server comes standard with one 270-watt power supply. Install three 270-watt power supplies to ensure redundancy and hot-swap capability for a typical con-

figuration. (See “Installing a hot-swap power supply” on page 85 for instructions.)

• 100 MHz front-side bus (FSB)

The FSB is the processor external bus. This bus is the interface between the processors and the system board. The FSB is also known as the processor/host bus.

• Large system memory

The memory bus in the server supports up to 16GB of system memory. The memory controller provides error correcting code (ECC) support for up to 16 industrystandard, 3.3 V, 168-pin, 8-byte, PCI, PC100 registered, dual inline memory modules (DIMMs). The memory controller also provides Chipkill™ memory protection. Chipkill memory protection is a technology

General information

5

that protects the system from a single chip failure on a

DIMM.

• System-management capabilities

The server comes with a Netfinity Advanced System

Management Processor on the system board. This processor, in conjunction with the Netfinity Manager provided on the ServerGuide CDs, enables you to manage the functions of the server locally and remotely. The Netfinity Advanced System Management Processor also provides system monitoring, event recording, and dial-out alert capability.

Note: The Netfinity Advanced System Management

Processor is sometimes referred to as the service processor.

Refer to “Netfinity Manager” on page 109 for more

information.

• Integrated network environment support

The server comes with an Ethernet controller on the system board. This Ethernet controller has an interface for connecting to 10-Mbps or 100-Mbps networks. The server automatically selects between 10BASE-T and

100BASE-TX. The controller provides full-duplex

(FDX) capability, which enables simultaneous transmission and reception of data on the Ethernet local area network (LAN).

• Redundant network-interface card (NIC)

The addition of an optional, redundant network-interface card (NIC) provides a failover capability to a redundant Ethernet connection. If a problem occurs with the primary Ethernet connection, all Ethernet traffic associated with this primary connection is automatically switched to the redundant NIC. This switching occurs without data loss and without user intervention.

• IBM ServerGuide CDs

The ServerGuide CDs included with IBM Netfinity servers provide programs to help you set up the server and install the network operating system (NOS). The ServerGuide program detects the hardware options installed, and provides the correct configuration program and device drivers. In addition, the ServerGuide

CDs include a variety of application programs such as

IBM Update Connector to help keep the server basic input/output system (BIOS) and microcode updated, and IBM Netfinity Manager for system management.

Note: The latest level of BIOS for the server is also available through the World Wide Web. Refer to

“Recovering BIOS” on page 24 for the appropri-

ate World Wide Web addresses and bulletinboard telephone numbers.

The server is designed to be cost-effective, powerful, and flexible. It uses peripheral component interconnect (PCI) bus architecture to provide compatibility with a wide range of existing hardware devices and software applications.

6


As always, the IBM server meets stringent worldwide certifications for power, electromagnetic compatibility (EMC), and

safety. See “Related service information” on page 195 for

additional information.

Reliability, availability, and serviceability

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 the server; that the 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 the server supports.

• Cooling fans with speed-sensing capability (hot-swap)

• Error correcting code (ECC) FSBs

• ECC L2 cache

• ECC memory

• Fast power-on self-test (POST)

• 45

°

C (113

°

F) normal operating temperature for hard disk drives

• Parity checking on the small computer system interface

(SCSI) bus and PCI buses

• Power Managed - Advanced Configuration and Power

Interface (ACPI) level

• System management monitoring via Intra-Integrated

Circuit (I

2

C) bus

• Ambient temperature monitoring

• Automatic error retry/recovery

• Automatic restart after a power failure

• Built-in temperature/fan/voltages monitoring

• Chipkill memory protection

• Fault-resistant startup

• Hot-swap drive bays

• Hot-swap hard disk drives

• Active PCI (hot-plug) adapter slots

• Information and diagnostic LED panels

• Menu-driven setup, system configuration, SCSISelect configuration, and diagnostic programs

• Memory scrubbing and Predictive Failure Analysis™

(PFA) (background and real time)

• Microcode and diagnostic levels available

• Netfinity Manager™ and LANDesk

®

enabled

• Netfinity Server Management

• NIC failover support

• Power and temperature monitoring

• Power-supply redundancy monitoring

• Predictive Failure Analysis™ (PFA) alerts

• Redundant Ethernet capabilities (with optional adapter)

• Redundant hot-swap cooling

• Redundant and hot-swap power supplies

• Remote Connect

• Remote system problem-determination support

• System auto-configuring from a configuration menu

• Upgradable POST, BIOS, diagnostics, and Netfinity

Advanced System Management Processor microcode

• Wake on LAN™ capability

General information

7

• Windows NT failover support

• Alert on LAN™ capability

• Backup BIOS switching by jumper

• Error codes and messages

• Integrated service processor subsystem provides control for remote system management

• Processor serial number access

• Standard cables present detection

• System error logging (POST and Netfinity Advanced

System Management Processor)

• Vital Product Data (VPD) on microprocessors, system board, power supplies, hot-swap-drive backplane, and power backplane

Start the server

Use the following procedure to start the server.

1. Turn on all external devices, such as the monitor.

Note: After you plug the power cord into an outlet, wait

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.

2. Press the power control button on the front of the server. The power-on light comes on and the poweron self-test (POST) begins.

• If the server is turned on and a power failure occurs, the server will start automatically when power is restored.

• The server can also be turned on by the Netfinity

Advanced System Management Processor.

When you turn off the server, observe the following precaution:

CAUTION:

The power control button on the device and/or the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

8


1

2

3

The server can be turned off as follows:

• You can turn off the server by pressing the power-control button on the front of the server.

Note: After turning off the server, wait at least five seconds before pressing the power-control button to turn on the server again.

• You can disconnect the server power cords from the electrical outlets to shut off all power to the server.

Note: Wait about 15 seconds after disconnecting the power cords for the system to stop running.

Watch for the system-power light on the information LED panel to stop blinking.

The following illustration shows the controls and indicators on the server.

Controls and indicators

Þ

1Ý

Þ

2Ý

Þ

3Ý

Power-control button: Press this button to manually turn on or off the server.

Reset button: Press this button to reset the server and run the power-on self-test (POST).

Hard-disk drive activity light: Each hot-swap drive has a hard–disk drive activity light. When this green light is flashing, the drive is being accessed.

General information

9

Þ

4Ý

Hard-disk drive status light: Each hot-swap drive has a hard-disk drive status light. With a

ServeRAID installation, if this amber light is on continuously, it means that the drive has failed.

Information LED panel

The information panel on the front of the server contains status lights.

The following illustration shows the server information panel.

RESET

SCSI ACT

LINK

OK

LINK OK

100

MB

100 MB

TX

RX

TX/RX INFO SYS ERROR

POWER

Þ

1Ý

Þ

2Ý

Þ

3Ý

Þ

4Ý

Þ

5Ý

Þ

5Ý

System power: When this green light is on, system power is present in the server. When this light flashes, the server is in standby mode (the system power supply is turned off and ac current is present). When this light is off, either a power supply, AC power, or a light has failed. The power light is located above and between the power-control button and the reset button.

Attention:

If this light is off, it does not mean there is no electrical current present in the server. The light might be burned out. To remove all electrical current from the server, you must unplug the server power cords from the electrical outlets.

Hard disk drive activity light: This green light is on when there is activity on a hard disk drive.

Ethernet-link status light: When this green light is on, there is an active connection on the Ethernet port. The Ethernet transmit/receive activity light is also located on the Ethernet (RJ-45) connector on the rear of the server.

Information light: When this amber light is on, the server power supplies are nonredundant or some other noncritical event has occurred. Check the diagnostic LED panel for more information

(see “Diagnostic panel LEDs” on page 20).

System error light: This amber light is on when a system error occurs. A light on the diagnostics

LED panel will also be on to further isolate the

error. (For more information, see “Diagnostic panel LEDs” on page 20.)

Ethernet transmit/receive activity light: When this green light is on, there is activity between the

10


Þ

7Ý server and the network. The Ethernet transmit/receive activity light is also located on the

Ethernet (RJ-45) connector on the rear of the server.

Ethernet speed 100 Mbps: When this green light is on, the Ethernet speed is 100 Mbps. When the light is off, the Ethernet speed is 10 Mbps.

General information

11

12


Diagnostics

This section provides basic troubleshooting information to help you resolve some common problems that might occur with the server.

If you cannot locate and correct the problem using the infor-

mation in this section, refer to “Symptom-to-FRU index” on page 153 for more information.

Diagnostic tools overview

The following tools are available to help you identify and resolve hardware-related problems:

• POST beep codes, error messages, and error logs

The power-on self-test (POST) generates beep codes and messages to indicate successful test completion or

the detection of a problem. See “POST” for more infor-

mation.

• 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. See “Diagnostic programs and error messages” on page 16 for more infor-

mation.

• Light path diagnostics

The server has light-emitting diodes (LEDs) to help you identify problems with server components. These

LEDs are part of the light-path diagnostics that are built into the server. By following the

path of lights

, you can quickly identify the type of system error that occurred.

See “Light path diagnostics” on page 18 for more infor-

mation.

• Error symptoms

These charts list problem symptoms, along with sug-

gested steps to correct the problems. See “Diagnosing errors” on page 27 for more information.

POST

When you turn on the server, it performs a series of tests to check the operation of server components and some of the options installed in the server. This series of tests is called the power-on self-test or POST.

If POST finishes without detecting any problems, a single beep sounds, the first screen of the operating system or application program appears.

If POST detects a problem, more than one beep sounds and

an error message appears on the screen. See “POST beep codes” on page 14 and “POST error messages” on page 14

for more information.

13

Notes:

1. If you have a power-on password or administrator password set, you must type the password and press

Enter, when prompted, before POST will continue.

2. A single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After you correct the cause of the first error message, the other error messages usually will not occur the next time you run the test.

POST beep codes

POST generates beep codes to indicate successful completion or the detection of a problem.

• One beep indicates the successful completion of

POST.

• More than one beep indicates that POST detected a

problem. For more information, see “Beep symptoms” on page 153.

POST error messages

POST error messages occur during startup when POST finds a problem with the hardware or detects a change in the hardware configuration. For a list of POST errors, see

“POST error codes” on page 171.

Event/error logs

The POST error log contains the three most recent error codes and messages that the system generated during

POST. The System Event/Error Log contains all error messages issued during POST and all system status messages from the Netfinity Advanced System Management Processor.

To view the contents of the error logs, start the Configura-

tion/Setup Utility program (see “Starting the Configuration/Setup Utility program” on page 43); then, select

Event/Error Logs from the main menu.

Small computer system interface messages

If you receive a SCSI error message, see “SCSI error codes” on page 181.

Note: If the server does not have a hard disk drive, ignore any message that indicates that the BIOS is not installed.

You will get these messages only when running the SCSI

Select Utility.

ServerGuide error symptoms

Look for symptoms in the left column of the following chart.

Probable solutions appear in the right column.

14


Setup

Netfinity Setup and

Installation CD

won’t start.

ServeRAID program cannot view all installed drives – or – cannot install NOS.

Action

• Be sure the system is a supported Netfinity server with a startable (bootable)

CD-ROM drive.

• If the startup (boot) sequence settings have been altered, be sure the

CD-ROM is first in the boot sequence.

• If more than one CD-ROM drive is installed, be sure that only one drive is set as the primary drive. Start the CD from the primary drive.

• Be sure there are no duplicate SCSI IDs or IRQ assignments.

• Be sure that the hard disk drive is connected properly.

The

Operating

System Installation

program continuously loops.

Free up more space on the hard disk.

ServerGuide won't start

your

NOS CD.

Can't install NOS – option is grayed out.

Be sure the NOS CD you have is supported by ServerGuide. See the

Netfinity Setup and Installation

CD label for a list of NOS versions supported.

Either there is no logical drive defined (ServeRAID systems) or the ServerGuide system partition is not present. Run the setup and configuration program.

TechConnect CD

Can't start

TechConnect CD.

Can't view publications from

TechConnect CD, or text is unreadable.

Action

Be sure you're starting the CD on a system with Microsoft Windows installed.

Be sure you have the Adobe reader installed (available from the TechConnect CD).

Diskette Factory CD

Get "time out" or

"Unknown host" errors

Action

Be sure you have access to the

Internet through FTP directly.

Diagnostics

15

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.

Diagnostic error messages indicate that a problem exists; they are not intended to be used to identify a failing part.

Troubleshooting and servicing of complex problems that are indicated by error messages should be performed by trained service personnel.

Sometimes the first error to occur causes additional errors.

In this case, the server displays more than one error message. Always follow the suggested action instructions for the

first

error message that appears.

The following sections contain the error codes that might appear in the detailed test log and summary log when running the diagnostic programs.

The error code format is as follows: fff-ttt-iii-date-cc-text message

where:

fff ttt

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.

is the three-digit failure code that indicates the exact test failure that was encountered.

iii date cc

is the three-digit device ID.

is the date that the diagnostic test was run and the error recorded.

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 errors.

16


Failed

This result occurs when the diagnostic test discovers an error.

User Aborted This result occurs when you stop the diagnostic test before it is complete.

Not Applicable This result occurs when you specify a diagnostic test for a device that is not present.

Aborted This result occurs when the test could not proceed because of the system configuration.

Warning This result occurs when a possible problem is reported during the diagnostic test, such as when a device that is to be tested is not installed.

Test Specific String This is additional information that you can use to analyze the problem.

Starting the diagnostic programs

You can press F1 while running the diagnostic programs to obtain Help information. You also can press F1 from within a help screen to obtain online documentation from which you can select different categories. To exit Help and return to where you left off, press Esc.

To start the diagnostic programs:

1. Turn on the server and watch the screen.

Note: To run the diagnostic programs, you must start the server with the highest level password that is set. That is, if an administrator password is set, you must enter the administrator password, not the power-on password, to run the diagnostic programs.

2. When the message F2 for Diagnostics appears, press F2.

3. Type in the appropriate password; then, press Enter.

4. Select either Extended or Basic from the top of the screen.

5. When the Diagnostic Programs screen appears, select the test you want to run from the list that appears; then, follow the instructions on the screen.

Notes:

a. If the server 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.

Diagnostics

17

d. You can run the USB interface test and the USB external loopback 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 information until after the diagnostic program has run.

Note: If you already are running the diagnostic programs,

begin with step 3.

To view the test log:

1. Turn on the server and watch the screen.

If the server is on, shut down the operating system and restart the server.

2. When the message F2 for Diagnostics appears, press F2.

If a power-on password or administrator password is set, the server prompts you for it. Type in the appropriate password; then, press Enter.

3. When the Diagnostic Programs screen appears, select

Utility from the top of the screen.

4. Select View Test Log from the list that appears; then, follow the instructions on the screen.

The system maintains the test-log data while the server is powered on. When you turn off the power to the server, the test log is cleared.

Diagnostic error message tables

For descriptions of the error messages that might appear

when you run the diagnostic programs, see “Diagnostic error codes” on page 160. If diagnostic error messages appear

that are not listed in those tables, make sure that the server has the latest levels of BIOS, Advanced System Management Processor, ServeRAID, and diagnostics microcode installed.

Light path diagnostics

The server has LEDs to help you identify problems with some server components. These LEDs are part of the light path diagnostics built into the server. By following the

path

you can quickly identify the type of system error that occurred.

18


Status LEDs are located on the following components:

• Information panel

• Hard disk drive trays

• Power supply

• Diagnostic panel

• System board

Power supply LEDs

The AC and DC power LEDs on the power supply provide

status information about the power supply. See “Installing a hot-swap power supply” on page 85 for the location of these

LEDs.

Þ

1Ý

Þ

2Ý

Þ

3Ý

Þ

4Ý

Þ

5Ý

Filler panel

AC power light

DC power light

Power supply handle

Power supply

The following table describes the AC and DC power LEDs.

AC power

LED

On

DC power

LED

On

Description and action

The power supply is on and operating correctly.

Diagnostics

19

AC power

LED

On

DC power

LED

Off

Description and action

There is a dc power problem.

Off Off

Possible causes:

1. The server is not turned on (the power LED is blinking on the front of the server).

Action: Press the power-control button to start the server.

2. The power supply has failed.

Action: Replace the power supply.

There is an ac power problem.

Possible causes:

1. There is no ac power to the power supply.

Actions: Verify that:

• The electrical cord is properly connected to the server.

• The electrical outlet functions properly.

2. The power supply has failed.

Action: Replace the power supply.

Diagnostic panel LEDs

The following illustration shows the LEDs on the diagnostics

panel inside the server. See Table 1 on page 22 for informa-

tion on identifying problems using these LEDs.

20


CPU

Memory

PCI

Bus A B C D

Power

Supply

1 2 3 4

Fan

DASD

NMI

SP Bus

Event Log

Non Red

Over Spec

Temp

Þ

1Ý

Þ

2Ý

System board connector

Diskette drive connector

The meanings of these LEDs are as follows:

CPU

Microprocessor fault

Memory

Memory fault

PCI Bus A (PCIA) PCI bus A fault

PCI Bus B (PCIB) PCI bus B fault

PCI Bus C (PCIC) PCI bus C fault

PCI Bus D (PCID) Not implemented at this time

Power supply 1

Power supply number 1 failure

Power supply 2


Power supply 3


FAN

Fan failure

DASD

NMI

SP Bus

Hard disk drive fault

Nonmaskable interrupt

Service processor failure

Event Log

NON RED

OVER SPEC

TEMP

Not implemented at this time.

Nonredundant power mode

Over specification

System temperature failure

Diagnostics

21

Notes:

1. The server does not support replaceable voltage regulator modules (VRMs).

2. The server supports a maximum of three PCI buses.

3. The server supports a maximum of three power supplies.

Light path diagnostics

You can use the light path diagnostics built into the server to quickly identify the type of system error that occurred. The server is designed so that LEDs remain illuminated when the server shuts down, as long as the power supplies are operating properly. This feature helps you to isolate the problem if an error causes the server to shut down.

If the system error LED (on the information LED panel) is not lit and no diagnostics panel LEDs are lit, it means that the light path diagnostics have not detected a system error.

If the system error LED (on the information LED panel) is lit, it means that a system error was detected. Check to see which of the LEDs on the diagnostics panel inside the server are lit and refer to the following table:

Table 1. Light path diagnostics

LED on

None

CPU

Memory

Cause

1. The system error log is 75% or more full or a PFA alert was logged. (See

“Diagnostic panel error LEDs” on page

157.)

2. Bad, missing, or mis-installed processor terminator.

One of the microprocessors has failed. (See

“Diagnostic panel error LEDs” on page 157.)

A memory error occurred. (See “Diagnostic panel error LEDs” on page 157.)

PCIA

PCIB

PCIC

PCID

PS1

PS2

An error occurred on PCI bus A. An adapter in PCI slot 1, or the system board, caused

the error. (See “Diagnostic panel error

LEDs” on page 157.)

An error occurred on PCI bus B. An adapter in PCI slot 2, 3, or 4, or the system board,

caused the error. (See “Diagnostic panel error LEDs” on page 157.)

An error occurred on PCI bus C. An adapter in PCI slot 5 or 6, or the system board,

caused the error. (See “Diagnostic panel error LEDs” on page 157.)


The first power supply has failed. (See


The second power supply has failed. (See


22


Table 1. Light path diagnostics

LED on

PS3

Fan

Cause

The third power supply has failed. (See


One of the fan assemblies has failed or is operating too slowly.

Note: A failing fan can also cause the TEMP and/or DASD LEDs to be on.

DASD

NMI

SP

(See “Diagnostic panel error LEDs” on page

157.)

A hot-swap hard disk drive has failed on

SCSI channel B. (See “Diagnostic panel error LEDs” on page 157.)

A nonmaskable interrupt occurred. (The

PCIA, PCIB, PCIC, or Memory LED will probably also be on.)

Note: The NMI LED can only be reset by comletely removing power from system.

(See “Diagnostic panel error LEDs” on page

157.)

The service processor has failed. (See


Event Log


Non Red

System is operating in non-redundant power

mode. (See “Diagnostic panel error LEDs” on page 157.)

Over Spec

The server is drawing more power than the power supplies are rated for. (See


Temp

The system temperature has exceeded the

maximum rating. (See “Diagnostic panel error LEDs” on page 157.)

Power checkout

Power problems can be difficult to troubleshoot. For instance, a short circuit can exist anywhere on any of the power distribution busses. Usually a short circuit will cause the power subsystem to shut down because of an overcurrent condition.

A general procedure for troubleshooting power problems is as follows:

1. Power off the system and disconnect the AC cord(s).

2. Check for loose cables in the power subsystem. Also check for short circuits, for instance if there is a loose screw causing a short circuit on a circuit board.

3. Remove adapters and disconnect the cables and power connectors to all internal and external devices until system is at minimum configuration required for

Diagnostics

23

power on (see "Minimum operating requirements" on

page 187).

4. Reconnect the AC cord and power on the system. If the system powers up successfully, replace adapters and devices one at a time until the problem is isolated.

If system does not power up from minimal configuration, replace FRUs of minimal configuration one at a time until the problem is isolated.

To use this method it is important to know the minimum con-

figuration required for a system to power up (see page 187).

For specific problems, see “Power error messages” on page

183.

Recovering BIOS

If the BIOS code in the server has become corrupted, such as from a power failure during a flash update, you can recover the BIOS using the recovery boot block and a BIOS flash diskette.

Note: You can obtain a BIOS flash diskette from one of the following sources:

• 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 the server.

The flash memory of the server consists of a primary page and a backup page. The J14 jumper controls which page is used to start the server. If the BIOS in the primary page is corrupted, you can use the backup page to start the server; then boot the BIOS Flash Diskette to restore the BIOS to the primary page.

To recover the BIOS:

1. Turn off the server and peripheral devices and disconnect all external cables and power cords; then, remove the cover.

2. Locate jumper J14 on the processor board (see

“System board jumpers” on page 56).

3. Move J14 to pins 1 and 2 to enable secondary boot block page.

4. Insert the BIOS flash diskette into the diskette drive.

5. Restart the server.

6. The system begins the power-on self-test (POST).

Select 1 – Update POST/BIOS from the menu that contains various flash (update) options.

7. When you are asked if you would like to move the current POST/BIOS image to the backup ROM location, type N.

Attention: Typing Y will copy the corrupted BIOS into the secondary page.

24


8. When you are asked if you would like to save the current code to a diskette, select N.

9. You will be asked to choose which language you wish to use. Select your language (0-7) and press Enter to accept your choice. You will be prompted to remove the diskette and press Enter to restart the system.

Remove the flash diskette from the diskette drive.

Attention: Do not press Enter to reboot the system at this time.

10. Power-off the server.

11. Move jumper J14 back to pins 2 and 3 to return to normal startup mode.

12. Restart the server. The system should start up normally.

Replacing the battery

IBM has designed this product with your safety in mind. The lithium battery must be handled correctly to avoid possible danger. If you replace the battery, you must adhere to the following instructions.

CAUTION:

When replacing the battery, use only IBM Part Number

33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.

Do not:

• Throw or immerse into water

• Heat to more than 100

°

C (212

°

F)

• Repair or disassemble

Dispose of the battery as required by local ordinances or regulations.

Note: In the U. S., call 1-800-IBM-4333 for information about battery disposal.

If you replace the original lithium battery with a heavy-metal battery or a battery with heavy-metal components, be aware of the following environmental consideration. Batteries and accumulators that contain heavy metals must not be disposed of with normal domestic waste. They will be taken back free of charge by the manufacturer, distributor, or representative, to be recycled or disposed of in a proper manner.

Note: After you replace the battery, you must reconfigure the server and reset the system date and time.

To replace the battery:

1. Read the information in “Before you begin” on page 63.

2. Follow any special handling and installation instructions supplied with the battery.

Diagnostics

25

3. Turn off the server and all attached devices and discon-

nect all external cables and power cords (see “Safety information” on page 196); then remove the top cover.

4. Locate the battery on the system board (see “System board component locations” on page 54).

5. Remove adapters as necessary so you can access the

battery. (See “Working with adapters” on page 68.)

6. Lift and remove the plastic dividers by pressing the latches on the top ends of the dividers toward the dividers and lifting the dividers from the server.

7. Remove the battery: a. Use one finger to lift the battery clip over the battery.

b. Use one finger to slightly slide the battery toward the rear of the server. The spring mechanism behind the battery will push it out toward you as you slide it forward.

c. Use your thumb and index finger to pull the battery from under the battery clip.

d. Ensure that the battery clip is touching the base of the battery socket by pressing gently on the clip.

8. Insert the new battery: a. Tilt the battery so that you can insert it into the front of the socket, under the battery clip.

b. As you slide it under the battery clip, press the battery down into the socket.

9. Reinstall any adapters that you removed.

10. Insert the plastic dividers into the divider guides.

11. Reinstall the top cover.

Note: You must wait approximately 20 seconds after you plug the power cord of the server into an electrical outlet before the power control button becomes active.

12. Start the Configuration/Setup Utility program and set

configuration parameters as needed. Refer to “Using the Configuration/Setup Utility program” on page 43.

26


Temperature checkout

Proper cooling of the system is important for proper operation and system reliability. For a typical Netfinity server, you should make sure:

• Each of the drive bays has either a drive or a filler panel installed

• Each of the power supply bays has either a power supply or a filler panel installed

• The top cover is in place during normal operation

• There is at least 50 mm (2 inches) of ventilated space at the sides of the server and 100 mm (4 inches) at the rear of the server

• The top cover is removed for no longer than 30 minutes while the server is operating

• The processor housing cover covering the processor and memory area is removed for no longer that ten minutes while the server is operating

• A removed hot-swap drive is replaced within two minutes of removal

• Cables for optional adapters are routed according to the instructions provided with the adapters (ensure that cables are not restricting air flow)

• The fans are operating correctly and the air flow is good

• A failed fan is replaced within 48 hours

In addition, ensure that the environmental specifications for

the system are met. See “Features and specifications” on page 3.

Note: The speed of the fans will increase if:

• One fan fails.

• Ambient temperature gets too high.

For more information on specific temperature error mes-

sages, see “Temperature error messages” on page 182.

Diagnosing errors

To find solutions to problems that have definite symptoms,

see “Error symptoms” on page 166.

If you cannot find the problem there, go to “Starting the diagnostic programs” on page 17 to test the server.

If you have just added new software or a new option and the server is not working, do the following before using the error symptoms table:

• Remove the software or device that you just added.

• Run the diagnostic tests to determine if the server is running correctly.

Diagnostics

27

• Reinstall the new software or new device.

Troubleshooting the Ethernet controller

This section provides troubleshooting information for problems that might occur with the 10/100 Mbps Ethernet controller.

Network connection problems

If the Ethernet controller cannot connect to the network, check the following:

• 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.

• Determine if the hub supports auto-negotiation. If not, try configuring the integrated Ethernet controller manually to match the speed and duplex mode of the hub.

• Check the Ethernet controller lights on the operator information panel.

These lights indicate whether a problem exists with the connector, cable, or hub.

— The Ethernet Link Status light illuminates when the Ethernet controller receives a LINK pulse from the hub. If the light is off, there might be a defective connector or cable, or a problem with the hub.

— The Ethernet Transmit/Receive Activity light illuminates when the Ethernet controller sends or receives data over the Ethernet Network. If the

Ethernet Transmit/Receive Activity light is off, make sure that the hub and network are operating and that the correct device drivers are loaded.

— The Ethernet Speed 100 Mbps light illuminates when the Ethernet controller LAN speed is

100 Mbps.

• Make sure that you are using the correct device drivers, supplied with 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).

28


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.

Table 2. Ethernet troubleshooting chart

Ethernet controller problem

Suggested Action

The server stops running when loading device drivers.

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.

Ethernet Link

Status light does not light.


• Make sure that the hub is turned on.

• Check all connections at the Ethernet controller and the hub.

• Check the cable. A crossover cable is required unless the hub has an

X

designation.

• Use another port on the hub.

• If the hub does not support autonegotiation, manually configure the

Ethernet controller to match the hub.

• If you manually configured the duplex mode, make sure that you also manually configure the speed.

• Run diagnostics on the LEDs.

Diagnostics

29

Table 2. Ethernet troubleshooting chart

Ethernet controller problem

Suggested Action

The Ethernet

Transmit/

Receive

Activity light does not light.


Note: The Ethernet Transmit/Receive

Activity LED illuminates only when data is sent to or by this Ethernet controller.

• Make sure that you have loaded the network device drivers.

• The network might be idle. Try sending data from this workstation.

• Run diagnostics on the LEDs.

• The function of this LED can be changed by device driver load parameters. If necessary, remove any LED parameter settings when you load the device drivers.

Data is incorrect or sporadic.


• Make sure that you are using

Category 5 cabling when operating the server at 100 Mbps.

• Make sure that the cables do not run close to noise-inducing sources like fluorescent lights.

The Ethernet controller stopped working when another adapter was added to the server.


• Make sure that the cable is connected to the Ethernet controller.

• Make sure that the 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.


• Run diagnostics for the Ethernet controller.

• Try a different connector on the hub.

• Reinstall the device drivers. Refer to the operating-system documentation and to the ServerGuide information.

30


Ethernet controller messages

The integrated Ethernet controller might display messages from the following device drivers:

• Novell™ NetWare™ or IntraNetWare Server ODI

• NDIS Adapter for level 2.01 (OS/2)

• NDIS Adapter for level 4.0 (Windows NT)

• SCO™ UNIX LLI

Novell NetWare or IntraNetWare server ODI driver messages

This section provides explanations of the error messages for the Novell NetWare or IntraNetWare server ODI driver, and suggested actions to resolve each problem.

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

PCNTNW-

NW-026

PCNTNW-

NW-054

PCNTNW-

NW-058

The MSM is unable to parse a required

custom keyword.

Explanation: The user entered an incorrect parameter keyword.

Action: Reload the driver using the correct keyword.

The adapter did not respond to the

initialization command.

Explanation: The adapter did not respond when the driver tried to initialize it.

Action: Verify that the Ethernet controller is enabled. If the Ethernet controller is

enabled, go to “Starting the diagnostic programs” on page 17 to run the

diagnostic programs.

The adapter did not respond to the

initialization command.

Explanation: The interrupt request (IRQ) setting might not be valid or the EEPROM information might be incorrect.

Action: Make sure the IRQ settings are correct in the Configuration/Setup Utility program. for information on setting the interrupt requests. If the IRQ settings are

correct, go to “Starting the diagnostic programs” on page 17 to run the


Diagnostics

31


PCNTNW-

NW-066

PCNTNW-

NW-071

PCNTNW-

NW-072

PCNTNW-

NW-073

PCNTNW-

NW-074

The cable might be disconnected from

the adapter.

Explanation: The cable might be disconnected from the server Ethernet port.

Action: Verify that a cable is connected to the Ethernet port.

The matching virtual adapter could not

be found.

Explanation: You tried to load another instance of the driver with a different I/O address. This new adapter could not be found.

Action: Verify that you installed an IBM

Netfinity 10/100 Fault Tolerant Adapter and make sure that the adapter is seated correctly. If the adapter is seated

correctly, go to “Starting the diagnostic programs” on page 17 to run the


A resource tag is unavailable.

Explanation: The driver tried to allocate some resources that were not available.

Action: Add more memory, or free some memory resources in the server. Then, restart the server.

Unable to allocate memory

Explanation: The driver failed to allocate the memory needed for normal operation.

Action: Add more memory, or free some memory resources in the server. Then, restart the server.

The hardware interrupt cannot be set.

Explanation: An attempt was made to initialize a given hardware interrupt. The attempt was not successful.



diagnostic programs. If you have an

Ethernet adapter installed, make sure that the adapter does not share an IRQ with any other device.

32



PCNTNW-

NW-075

PCNTNW-

NW-079

PCNTNW-

NW-086

PCNTNW-

NW-087

PCNTNW-

NW-091

The Multiple Link Interface Driver

(MLID) cannot be registered with the

Link Support Layer (LSL).

Explanation: An error occurred while the driver was trying to register with the LSL.

Action: Check the version of the

NetWare or IntraNetWare Operating

System. Make sure that this driver is correct for the version of NetWare or

IntraNetWare that you are using. Restart the server.

The Multiple Link Interface Driver

(MLID) did not initialize MSMTx Free

Count.

Explanation: The MSMTx Free Count is not initialized correctly.

Action: Restart the server. If the problem

persists, go to “Starting the diagnostic programs” on page 17 to run the


The driver parameter block is too small.

Explanation: The driver parameter block is too small.

Action: Restart the server. If the

problem persists, go to “Starting the diagnostic programs” on page 17 to run

the diagnostic programs.

The media parameter block is too small.

Explanation: The driver media parameter block is too small.

Action: Restart the server. If the

problem persists, go to “Starting the diagnostic programs” on page 17 to run

the diagnostic programs.

The hardware configuration conflicts.

Explanation: You tried to load a new frame type for the existing controller. The hardware assumptions made in doing so are incorrect. This error can also occur if you try to specify a mode (such as, redundancy) that conflicts with another specified mode.

Action: Make sure that the hardware configuration matches the software settings.

Diagnostics

33


PCNTNW-

NW-126

PCNTNW-

NW-127

PCNTNW-

NW-164

PCNTNW-

NW-165

PCNTNW-

NW-167

The group bit in the node address override was cleared.

Explanation: The IEEE address has a group bit that indicates that an address belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. You tried to enter a source address with this bit set. The driver cleared the group bit of the source address.

Action: None necessary, message is for information only.

The local bit in the node address override was set.

Explanation: The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit must be set. You entered an address without the local bit set. The driver has set the local bit.


The device was not found.

Explanation: The driver cannot find an

Ethernet controller in the server.




The device was not found at

IOADDRESS.

Explanation: The Ethernet controller cannot be found at the I/O address specified.

Action: The Ethernet controller does not require a parameter for the I/O address.

Remove the I/O address parameter.

PCI scan specified, device not found.

Explanation: The driver cannot locate the Ethernet controller on the PCI bus.

Action: Verify that the Ethernet controller is enabled. If the problem persists, go to

“Starting the diagnostic programs” on page 17 to run the diagnostic programs.

34



PCNTNW-

NW-180

The DMA parameter is not necessary

for PCI device.

Explanation: The Ethernet controller does not require a DMA setting.


Network driver interface specification 2.01

(OS/2) driver messages

This section provides explanations of the error messages for the NDIS 2.01 (OS/2) drivers, and suggested actions to resolve each problem.

Table 4. NDIS 2.01 (OS/2) driver messages for the Ethernet controller

PCNTND-1

PCNTND-6

PCNTND-7

PCNTND-8

PCNTND-9

Unable to open the Protocol Manager.

Explanation: The NDIS stack is not configured correctly.

Action: Check and correct the configuration.

Out of memory while allocating buffers.

Explanation: The driver could not allocate the requested buffers.

Action: Check the system configuration.

Edit the PROTOCOL.INI file to reduce the number of Txbuffers and Rxbuffers specified for the driver.

A Protocol Manager device error occurred.



Bad status for the Protocol Manager.

Explanation: The NDIS stack is not configured correctly in the

PROTOCOL.INI file.


Cannot find the PROTOCOL.INI entry.


PROTOCOL.INI file.


Diagnostics

35


PCNTND-10 The Protocol Manager Input Output

Control (IOCTL) failed.


PROTOCOL.INI file.


PCNTND-11 Protocol Manager registration failed.



PCNTND-15 Device not found.


Ethernet controller in the server.




PCNTND-16 PCI scan specified, device not found.

Explanation: The driver cannot locate the Ethernet controller on the PCI bus.




PCNTND-21 The adapter failed the checksum test.


Ethernet controller.




PCNTND-23 WARNING: PCNET IRQ found =

xx

Explanation: The interrupt request (IRQ) setting ( xx

) in the PROTOCOL.INI file does not match the hardware IRQ setting.

Action: Remove the IRQ setting from the

PROTOCOL.INI file or change the IRQ setting in the PROTOCOL.INI file to match the IRQ setting shown in the PCI

Slot/Device Information selection of the

Advanced Setup menu in the

Configuration/Setup Utility program.

36



PCNTND-24 WARNING: PCNET IRQ does not match PROTOCOL.INI.

Explanation: The interrupt request (IRQ) setting in the PROTOCOL.INI file does not match the hardware IRQ setting.

Action: Remove the IRQ setting from the

PROTOCOL.INI file or change the IRQ setting in the PROTOCOL.INI file to match the IRQ setting shown in the PCI

Slot/Device Information selection of the

Advanced Setup menu in the


PCNTND-25 PCI scan specified, PCI bus not found!

Explanation: The driver cannot locate the PCI bus.

Action: Run the diagnostic programs.

PCNTND-29 WARNING: DMA number is not necessary for PCI device.

Explanation: The Ethernet controller does not require a DMA setting.

Action: Remove the DMA setting in the

PROTOCOL.INI file.

PCNTND-33 PCNET device with specified IOBASE is already in use.

Explanation: The specified I/O address number is already in use by another

Ethernet controller or device.

Action: Remove the I/O address setting in the PROTOCOL.INI file.

NDIS 4.0 (Windows NT) driver messages

This section contains the error messages for the NDIS 4.0 drivers. The explanation and recommended action are included with each message.

Table 5. NDIS (Windows NT) driver messages for the

Ethernet controller

PermaNet™

Server:

No Secondary Adapter Found.

Grouping Mode is disabled.

Explanation: The failover option requires an adapter that is compatible with the device driver of the Ethernet controller on the system board. No such adapter was found.

Action: Make sure the correct adapter is installed.

Diagnostics

37

Table 5. NDIS (Windows NT) driver messages for the

Ethernet controller

PermaNet

Server:

PermaNet

Server:

Problem Occurs on the Primary

Adapter. Switching over to the

Secondary Adapter.

Explanation: The system detected a problem with the primary Ethernet connection and has transferred all network traffic to the secondary Ethernet controller.

Action: identify the cause of the failure on the primary Ethernet connection.

Restoring the operational state of the primary connection will cause the network traffic to automatically transfer to the primary Ethernet controller.

Switching back to Primary Adapter.

Explanation: The primary Ethernet connection is now operating correctly.

Network traffic will automatically transfer to the primary Ethernet controller.

Action: None needed, message is for information only.

UNIX messages

This section provides descriptions of the Ethernet error messages for the SCO UNIX LLI driver, and suggested actions to resolve each problem.

Table 6. UNIX LLI driver messages for the Ethernet controller

pnt0-2

PCI search specified, PCI device not found!

Explanation: The driver cannot locate the

Ethernet controller on the PCI bus.

Action:

• Run the NETCONFIG program to search for another Ethernet controller

• Verify that the Ethernet controller is enabled. If the Ethernet controller is enabled, run the diagnostic programs.

38



pnt0-6 pnt0-7

Cannot allocate memory for the adapter during an interrupt. Please check the

Streams parameters.

Explanation: On a SunSoft Solaris system, this message indicates that the system is out of

Streams memory blocks.

Action: Use the CRASH utility to increase the number of Streams memory blocks. Modify the interrupt request (IRQ) settings in the

Configuration/Setup Utility program, or run the

NETCONFIG program to match the hardware settings.

Cannot allocate memory for the adapter during reset. Please check the Streams parameters.

Explanation: The system is out of Streams memory blocks.

Action: Use the CRASH utility to increase the number of Streams memory blocks.

pnt0-11

Device not found!



Action: Verify that the Ethernet controller is enabled. If the Ethernet controller is enabled, run the diagnostic programs.

pnt0-12 Device failed checksum test!




pnt0-13 add_intr_handler failed! Interrupts already enabled.

Explanation: The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Action: Modify the hardware settings.

pnt0-14

Cannot locate hardware.

Explanation: The SunSoft Solaris driver cannot find any Ethernet controller.


Diagnostics

39


pnt0-15 No more devices to open.

Explanation: The SunSoft Solaris driver cannot find any more Ethernet controllers.

Action: Verify that additional IBM Netfinity

10/100 Fault Tolerant Adapters are present or replace the Ethernet adapter that fails to respond. If the problem persists, run the diagnostic programs.

pnt0-17 Device fault...Reset initiated!

Explanation: The SunSoft Solaris driver has been reset due to a device fault.

Action: Verify that additional IBM Netfinity

10/100 Fault Tolerant Adapters are present or replace the Ethernet adapter that fails to respond. If the problem persists, run the diagnostic programs.

pnt0-19 IRQ found for PCnet hardware does not match space.c (or pnt.conf)!

Explanation: This is a warning message referring to the interrupt request (IRQ) that the

SunSoft Solaris driver found in the system.

Action: Ignore this message if you are sure that this is what you want to do. Otherwise, run the NETCONFIG program to match the hardware settings

pnt0-20 add_intr_handler failed! Unknown interrupt type.


Action:

• Modify the hardware settings.

• Run the NETCONFIG program to search for another Ethernet controller.

pnt0-21 add_intr_handler failed! Out of range interrupt number.


Action:



40



pnt0-22

add_intr_handler failed! Out of range IPL.


Action: Modify the hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-23 add_intr_handler failed! Vector already occupied.


Action: Modify the hardware settings.

pnt0-24 add_intr_handler failed! Vector already shared at different IPL.


Action:



pnt0-26 The DMA number is not necessary for PCI device.

Explanation: The IBM Netfinity 10/100 Fault

Tolerant Adapter does not require a DMA setting.

Action: Edit the SPACE.C file to delete the

DMA parameter.

pnt0-29

The IRQ number is already in use.

Explanation: The specified I/O address is already in use.

Action: Run the NETCONFIG program to modify the hardware settings.

pnt0-31 I/O address is not necessary for the PCI

device.

Explanation: The I/O address specified is not required.

Action: Remove the assigned I/O address specified for the Ethernet controller.

Diagnostics

41

42


Configuring the server

In addition to the ServerGuide CDs, you can use the following configuration programs to customize your server hardware:

• Configuration/Setup Utility

The Configuration/Setup Utility program is part of the

basic input/output system

(

BIOS

) code that comes with the server. You can use this program to configure serial and parallel port assignments, change interrupt request (IRQ) settings, change the drive startup sequence, set the date and time, and set passwords.

See “Using the Configuration/Setup Utility program” for

more information.

• SCSISelect Utility

With the built-in SCSISelect Utility program, you can configure the devices attached to the integrated SCSI controller. Use this program to change default values, resolve configuration conflicts, and perform a low-level

format on a SCSI hard disk drive. See “Using the

SCSISelect utility program” on page 50 for more infor-

mation.

• ServeRAID programs

The ServeRAID programs come with the optional ServeRAID adapters and with server models that have a

ServeRAID adapter preinstalled. If a ServeRAID adapter has been installed in the server, you must use the ServeRAID configuration program to define and configure the disk-array subsystem before you install the operating system.

• ServerGuide CDs

The ServerGuide CDs include software setup and installation tools specifically designed for IBM Netfinity servers. You can use these CDs during the initial installation of the server to configure the server hardware and simplify the network operating system installation. The ServerGuide CDs also contain a collection of application programs, which you can install after the server is up and running.

Using the Configuration/Setup Utility program

This section provides the instructions needed to start the

Configuration/Setup Utility program and descriptions of the menu choices available.

Starting the Configuration/Setup Utility program

To start the Configuration/Setup Utility program:

1. Turn on the server and watch the monitor screen.

2. When the message Press F1 for Configuration/Setup appears, press F1.

43

Note: If you have set both levels of passwords (user and administrator), you must enter the administrator password to access the full Configuration/Setup menu.

3. Follow the instructions that appear on the screen.

Choices available from the

Configuration/Setup main menu

From the Configuration/Setup Utility main menu, you can select settings that you want to change. The Configuration/Setup Utility main menu is similar to the following:

IBM Netfinity Setup - © IBM Corporation 1998

Configuration/Setup Utility

•

•

System Summary

System Information

•

•

•

•

•

•

Devices and I/O Ports

Date and Time

System Security

Start Options

Advanced Setup

Error Logs

Save Settings

Restore Settings

Load Default Settings

Exit Setup

<F1> Help < > < > Move

<Esc> Exit <Enter> Select

Notes:

1. You can press F1 to display Help information for a selected menu item.

2. The choices on some menus might differ slightly, depending on the BIOS version in the server.

Descriptions of the choices available from the main menu are as follows:

• System Summary

Select this choice to display configuration information.

This includes the type and speed of the microprocessors and the amount of memory installed.

Changes that you make to configuration settings appear on this summary screen. You cannot edit the fields.

This choice appears on both the full and limited Configuration/Setup Utility menus.

• System Information

Select this choice to display information about the server. Changes that you make on other menus might appear on this summary screen. You cannot edit any fields. The System Information choice appears only on the full Configuration/Setup Utility main menu.

— Product Data

44


Select this choice to view system information, such as the machine type and model, the server serial number, and the revision level or issue date of the BIOS stored in the flash electronically erasable programmable ROM (EEPROM).

— System Card Data

Select this choice to view vital product data (VPD) for some server components.

• Devices and I/O Ports

Select this choice to view or change the assignments for devices and input/output ports. This choice appears only on the full Configuration/Setup Utility main menu.

This choice also allows you to enable or disable the integrated SCSI, video, and Ethernet controllers.

— The default setting is Enable for all the controllers.

If you select Disable, the system will not configure the disabled device and the operating system will not see the device. (This is equivalent to unplugging the device.)

— If the on-board SCSI controller is disabled and no other controller and mass storage device are installed, operating system startup cannot occur.

— If the video controller is disabled and no video adapter is installed, the server will have no video capability.

• Select System Service Processor Settings to view the interrupt-request setting (IRQ) used by the

Advanced System Management Processor (system service processor). You can then use the arrow keys to select a new IRQ setting for the Advanced System

Management Processor from the list of available choices.

• Date and Time

Select this choice to set the system date and time and to change the system time sent to the Advanced System Management Processor (service processor) when the server is started. This choice appears only on the full Configuration/Setup Utility main menu.

The system time is in a 24-hour format: hour:minute:second.

You can set a time delta to be added or subtracted from the system time that is sent to the service processor

(Advanced System Management Processor) each time the server is started. Use the number keys to enter the hours and minutes and + or

−

to add or subtract from the system time. If you want the system clock time to be the same as the Advanced System Management

Processor clock time, leave the value set at its default of 0.

• System Security

Select this choice to set passwords or a system owner’s name. This choice appears only on the full

Configuration/Setup Utility main menu.

You can implement two levels of password protection:

Configuring the server

45

— Power-on Password

Select this choice to set or change a power-on

password. See “Using passwords” on page 48 for

more information.

— Administrator Password

Select this choice to set or change an administrator password.

Attention:

If an administrator password is set and then forgotten, it cannot be overridden or removed. You must replace the system board.

The administrator password provides access to all choices on the Configuration/Setup Utility main menu. You can set, change, or delete both the administrator and power-on passwords, and allow a power-on password to be changed by the user.

See“Using passwords” on page 48 for more infor-

mation.

•

Start Options

Select this choice to view or change the start options.

This choice appears only on the full Configuration/Setup Utility main menu. Start options take effect when you start your server.

You can select keyboard operating characteristics, such as the keyboard speed. You also can specify whether the keyboard number lock starts on or off. You also can enable the server to run without a diskette drive, monitor, or keyboard.

The server uses a startup sequence to determine the device from which the operating system loads. For example, you can define a startup sequence that checks for a startable diskette in the diskette drive, then checks the hard disk drive in bay 1, and then checks a network adapter.

If the Boot Fail Count choice is enabled, you can restore the BIOS system defaults after three consecutive boot failures. If this choice is disabled, the BIOS system defaults can only be loaded from the Configuration/Setup Utility main menu.

You can enable a virus-detection test that checks for changes in the master boot record at startup.

•

Advanced Setup

Select this choice to change values for advanced hardware features, such as cache control, and PCI configuration. This choice appears only on the full


A warning message appears above the choices on this menu to alert you that the system might malfunction if these options are configured incorrectly. Follow the instructions on the screen carefully.

— Processor Serial Number Access

Select this choice to identify if the microprocessor serial number in the microprocessor is readable.

— System Partition Visibility

46


Select this choice to identify if the System Partition is visible. To make System Partition visible, set this value to

Visible

. To make System Partition invisible, set this value to

Hidden

.

— Core Chipset Control

Select this choice to modify settings that control features of the core chip set on the system board.

Attention: Do not make changes here unless directed to do so by an IBM authorized service representative.

— PCI Slot/Device Information

Select this choice to view and identify system resources used by PCI devices. PCI devices automatically communicate with the server configuration information. This usually results in automatic configuration of a PCI device.

Attention: You must use the menu selections to save custom settings for the PCI Slot/Device

Information choice. The save, restore and load default settings choices on the main menu of the

Configuration/Setup Utility do not save the PCI

Slot/Device Information settings.

After making changes, select:

– Save and exit the PCI Utility to save the changes and return to the Advanced Setup choice.

– Exit the PCI Utility without saving

changes to ignore the changes, restore the previous settings, and return to the

Advanced Setup choice.

PCI Device Control allows you to enable or disable the PCI slots from this menu.

– The default setting is Enable for all the PCI slots. If you select Disable, the system will not configure the disabled device and the operating system will not see the device.

(This is equivalent to unplugging the device.)

— Cache Control

Select this choice to enable or disable the microprocessor cache. In addition, you can define the microprocessor cache type as write-back (WB) or write-through (WT). Selecting write-back mode will provide the maximum system performance.

— Memory Settings

Select this choice to manually enable a bank of memory.

If a memory error is detected during POST or memory configuration, the server can automatically disable the failing memory bank and continue operating with reduced memory capacity. If this occurs, you must manually enable the memory bank after the problem is corrected. Select

Memory Settings from the Advanced Setup menu, use the arrow keys to highlight the bank that you want to enable; then, use the arrow keys to select Enable.


47

— Hot Swap PCI Slot Power Control

Select this choice to manually force power on to any of the six Active PCI (hot-plug) slots. This is used for PCI adapters that do not have the presence detect pins that the system hot-plug controller uses to turn power on to a slot.

• System Service Processor Settings

Select this choice to view the interrupt-request setting

(IRQ) used by the Advanced System Management Processor (system service processor). You can then use the arrow keys to select a new IRQ setting for the

Advanced System Management Processor from the list of available choices.

•

Event Logs

Select this choice to view or clear error logs.

— Select POST Error Log to view the three most recent error codes and messages that the system generated during POST.

Select Clear error logs from the POST Error Log menu to clear the error log.

— Select System Event/Error Log to view the system event/error log. The system event/error log contains all the system error and warning messages that the system has generated. You can use the arrow keys to move between pages in the system event/error log.

Select Clear error logs from the System

Event/Error Log menu to clear the error or event log.

• Save Settings

Select this choice to save the customized settings.

• Restore Settings

Select this choice to delete the changes and restore the previous settings.

• Load Default Settings

Select this choice to cancel the changes and restore the factory settings.

• Exit Setup

If you have made any changes, the program will prompt you to save the changes or exit without saving the changes.

Using passwords

The System Security choice appears only on the full Configuration/Setup Utility menu. After you select this choice, you can implement two levels of protection: power-on password and administrator password.

Power-on password

After you set a power-on password, you can enable the unattended-start mode. This locks the keyboard and mouse, but allows the server to start the operating system.

48


The keyboard and mouse remain locked until you enter the correct password.

You can use any combination of up to seven characters (A–

Z, a–z, and 0–9) for the power-on password. Keep a record of the password in a secure place. If you forget the poweron password, you can regain access to the server by removing the battery and then installing the battery, or by overrid-

ing or bypassing the power-on password; see “Setting the password override jumper”.

Setting the password override jumper:

When a power-on password is set, POST does not complete until you enter the password. If you forget the power-on password, you can regain access to the server through either of the following methods:

• Enter the administrator password at the power-on prompt, if an administrator password has been set.

(See “Administrator password” on page 50 for details.)

Start the Configuration/Setup Utility program and

change the power-on password. See “Power-on password” on page 48.

• Change the position of the jumper on J15 to bypass the power-on password check. You can then start the Configuration/Setup Utility program and change the power-

on password. See “System board component locations” on page 54 for the location of J15.

Notes:

1. Turn off the server, and disconnect all power cords before moving any jumpers.

2. Jumpers J19 and J3 are located on the same jumper block as jumper J15 on the system board. These jumpers are set to

Disabled

. Do not change the settings on these jumpers.

Attention: If you change the settings on these jumpers, the server will fail.

Jumper name

J15 Power-on password override

Description

Changing the position of this jumper bypasses the power-on password check if the jumper has been moved since the server was last powered on. You do not need to move the jumper back to the default position after the password is overridden.

The default position is a jumper on pins 1 and 2.

Changing the position of this jumper does not affect the administrator password check if an administrator password is set.

Table 7. Jumper J15 on the system board

For more information on jumper locations, see “Changing jumper positions” on page 85.


49

Administrator password

Select this choice to set an administrator password. The administrator password provides access to all choices on the Configuration/Setup Utility main menu. You can set, change, or delete both the administrator and power-on passwords, and allow a power-on password to be changed by the user.

Attention: If an administrator password is set and then forgotten, it cannot be overridden or removed. You must replace the system board.

The following table provides a summary of the password features.

Table 8. Power-on and administrator password features

Type of password

Power-on password

Administrator password

Administrator

and

power-on password

Results

• Enter the password to complete the system startup.

• All choices are available on the


• No password is required to start the system.

• Enter the password to access the


• All choices are available on the


• You can enter either password to complete the system startup.

• The administrator password provides access to all choices on the

Configuration/Setup Utility main menu. You can set, change, or delete both the administrator and power-on passwords, and allow a power-on password to be changed by the user.

• The power-on password provides access to a limited set of choices on the Configuration/Setup Utility main menu. This limited access might include changing or deleting the power-on password.

Using the SCSISelect utility program

SCSISelect is a built-in, menu-driven configuration utility program that you can use to:

• View the default SCSI IDs

• Locate and correct configuration conflicts

• Perform a low-level format on a SCSI hard disk

50


The following sections provide the instructions needed to start the SCSISelect Utility and descriptions of the menu choices available.

Note: If the server has a RAID adapter installed, use the configuration method supplied with the RAID adapter to view or change SCSI settings for attached devices.

Starting the SCSISelect utility program

To start the SCSISelect utility program:

1. Turn on the server.

2. When the

<<< Press <CTRL><A> for SCSISelect™

Utility! >>> prompt appears, press Ctrl+A.

Note: If an administrator password has been set, a prompt appears asking you to enter the password to start the SCSISelect Utility program.

3. When prompted, select either channel A (internal) or channel B (external).

4. Use the arrow keys to select a choice from the menu.

• Press Esc to return to the previous menu.

• Press the F5 key to switch between color and monochrome modes (if the monitor permits).

5. Follow the instructions on the screen to change the settings of the selected items; then, press Enter.

Choices available from the SCSISelect menu

The following choices appear on the SCSISelect Utility menu:

•

Configure/View Host Adapter Settings

Select this choice to view or change the SCSI controller settings. To reset the SCSI controller to its default values, press F6; then, follow the instructions that appear on the screen.

You can view or change the following controller settings:

— Host Adapter SCSI ID

Select this choice to view the SCSI controller ID, normally 7.

— SCSI Parity Checking

Select this choice to view the assigned value of

Enabled.

— Host Adapter SCSI Termination

Select this choice to view the assigned value of

Enabled.

— Boot Device Options

Select this choice to configure startable device parameters. Before you can make updates, you must know the ID of the device whose parameters you want to configure.

— SCSI Device Configuration

Select this choice to configure SCSI device parameters. Before you can make updates, you


51

must know the ID of the device whose parameters you want to configure.

Note: The Maximum Sync Transfer Rate represents the transfer rate for Ultra SCSI devices.

– The transfer rate for Ultra3 SCSI LVD devices is 160.0

– The transfer rate for Ultra2 SCSI LVD devices is 80.0

– The transfer rate for Fast SCSI devices is 20.0

— Advanced Configuration Options

Select this choice to view or change the settings for advanced configuration options.

•

SCSI Disk Utilities

Select this choice to view the SCSI IDs that are assigned to each device or to format a SCSI device.

To use the utility program, select a drive from the list.

Read the screens carefully before making a selection.

Note: If you press Ctrl+A before the selected drives are ready, an Unexpected SCSI Command Failure screen might appear. Restart the server and watch the SCSISelect messages as each drive spins up. After the drive that you want to view or format spins up, press Ctrl+A.

52


Installing options

This chapter provides instructions to help you add options to the server.

Expanded view of the Netfinity 6000R

88

Þ

1Ý

Terminator card

Þ

2Ý

Microprocessor

Þ

3Ý

Hot-swap fans

Þ

4Ý

Hot-swap drive tray assembly

Þ

5Ý

Filler panel for hot-swap drive tray

Þ

6Ý

Filler panel for power supply bay

Þ

7Ý

Power supply

Þ

8Ý

Diagnostics panel

53

Þ

9Ý

Hot-swap fans

Þ

10Ý

System board

Þ

11Ý

Service processor card

Þ

12Ý

Memory board

Þ

13Ý

Dual inline memory module

Component locations

This section provides illustrations of the system board, Diagnostic LED panel, memory board, and Advanced System

Management Interconnect board component locations.

System board component locations

The following illustrations detail certain locations on the system board.

Note: The illustrations in this document might differ slightly from your hardware.

System board connectors:

The following illustration shows the location of connectors on the system board.

Þ

1Ý

Microprocessor slot 1 (J34)

Þ

2Ý


Þ

3Ý


Þ

4Ý


Þ

5Ý

Memory board (J40)

Þ

6Ý

PCI slot 2 64-bit 66 MHz (J51)

Þ

7Ý


54


Þ

8Ý


Þ

9Ý


Þ

10Ý


Þ

11Ý

PCI hot-plug switch card (J1)

Þ

12Ý


Þ

13Ý

Battery

System board cable connectors:

The following illustration shows the location of the cable connectors on the system board.

Þ

1Ý

Power signal (J16)

Þ

2Ý

Diagnostic panel (J18)

Þ

3Ý

IDE (J21)

Þ

4Ý

120 mm fan (J30)

Þ

5Ý

Main power (J71)

Þ

6Ý

Internal SCSI (J38)

Þ

7Ý

External SCSI (J39)

Þ

8Ý

Advanced System Management Interconnect board

(J69, J68, J67)

Þ

9Ý

120 mm fan (J49)

I/O external port connectors:

The following illustration shows the location of the input/output external port connectors on the system board.

Installing options

55

Þ

1Ý

Keyboard (bottom), mouse (top) (J64)

Þ

2Ý

Serial A (bottom), Serial B (top) (J60)

Þ

3Ý

Parallel (J63)

Þ

4Ý

Video (J62)

Þ

5Ý

Ethernet (J79)

Þ

6Ý

USB 1, USB 2 (J61)

System board jumpers:

The following illustration shows the location of the flash ROM page swap jumper

(J14) and power-on password override jumper (J15) on the system board. Jumper J14 is located at the top of the jumper block, and jumper J15 is located immediately below jumper J14.

56


Þ

1Ý

Flash ROM page swap jumper (J14)

Þ

2Ý

Power-on password override jumper (J15)

Þ

3Ý

Reserved (J19)

Þ

4Ý

Reserved (J3)

Notes:

1. Turn off the server; then, disconnect all power cords and external cables. before moving any jumpers.

2. Jumpers J19 and J3 are located on the same jumper block as jumpers J14 and J15 on the system board.

These jumpers are set to

Disabled

. Do not change the settings on these jumpers.

Attention: If you change the settings on these jumpers, the server will fail.

3. See “Changing jumper positions” on page 85 for addi-

tional information on setting jumpers.

Jumper name

J14 Flash ROM page swap

Description

The default position is a jumper installed on pins 2 and 3.

See “Recovering BIOS” on page 24

for additional information.

Table 9. Jumpers J14 and J15 on the system board

Installing options

57

Jumper name

J15 Power-on password override

Description

Changing the position of this jumper bypasses the power-on password check if the jumper has been moved since the server was last powered on. You do not need to move the jumper back to the default position after the password is overridden.

The default position is a jumper on pins 2 and 3.

Changing the position of this jumper does not affect the administrator password check if an administrator password is set.

See “Power-on password” on page

48 for additional information on the

power-on password.

Table 9. Jumpers J14 and J15 on the system board

Table 10. Jumper setback table

J13

H

H

J27 J28

L

L

L

H

J29

H

L

Bus Ratio

7:1

8:1

Core

Frequency

700

800

The following illustration shows the location of the microprocessor speed (core-frequency-selection) jumper block on the system board. The jumpers on this block are in the following order, from top to bottom: J13, J27, J28, and J29.

See “Installing a microprocessor kit” on page 81 for the

jumper speed settings.

Note: Any system-board jumper blocks that are not shown in the illustrations in this book are reserved.

58


Microprocessor speed jumpers

J13

J27

J28

J29

System board LED locations

The following illustration shows the location of the lights on the system board.


Installing options

59

Þ

1Ý

Microprocessor 1 error light

Þ

2Ý

Microprocessor or terminator card present lights

Þ

3Ý


Þ

4Ý


Þ

5Ý

POST OK light

Þ

6Ý


Þ

7Ý

PCI slot power-on light

Þ

8Ý

PCI slot attention lights

Diagnostic panel LEDs

The following illustration shows the location of the LEDs on the Diagnostic panel. The Diagnostic panel LEDs are visible through a special cutout area located to the left of the coverrelease latch on the top cover. However, to determine the exact location of the error condition in the server, you might need to remove the top cover to view the location of the error

LED on the Diagnostic panel.

Note: The Diagnostic panel is also called the LED card.

60


CPU

Memory

PCI

Bus A B C D

Power

Supply

1 2 3 4

Fan

DASD

NMI

SP Bus

Event Log

Non Red

Over Spec

Temp

Þ

1Ý


Þ

2Ý

Diskette drive connector

The meanings of these LEDs are as follows:

CPU

Microprocessor fault

Memory

Memory fault

PCI Bus A (PCIA) PCI bus A fault

PCI Bus B (PCIB) PCI bus B fault

PCI Bus C (PCIC) PCI bus C fault

PCI Bus D (PCID) Not implemented at this time.

Power supply 1


Power supply 2


Power supply 3


FAN

Fan failure

DASD

NMI

SP Bus

Hard disk drive fault

Nonmaskable interrupt

Service processor failure

Event Log

NON RED

OVER SPEC

TEMP


Nonredundant power mode

Over specification

System temperature failure

Installing options

61

Notes:


2. The server supports a maximum of three PCI buses.

3. The server supports a maximum of three power supplies.

4. See “Light path diagnostics” on page 22 for a detailed

description of these LEDs.

Memory board component locations

The following illustration shows the location of the dual inline memory module (DIMM) connectors and error LEDs on the memory board.

Notes:

1. The illustrations in this document might differ slightly from your hardware.

2. Some of the DIMM error LEDs are not visible in this illustration. The memory board contains 16 error LEDs; that is, one error LED for each DIMM connector.

Þ

1Ý

Memory slot 1

Þ

2Ý

Memory slot 9

Þ

3Ý

Error LEDs

Þ

4Ý

Memory slot 13

Þ

5Ý

Error LEDs

Þ

6Ý

Memory slot 5

62


Advanced System Management

Interconnect board component locations

The following illustration shows the connectors and lights for the Netfinity Advanced System Management Interconnect board.

Notes:


2. The Advanced System Management Interconnect board is also called the service processor card.

Þ

1Ý

Serial port

Þ

2Ý

Advanced System Management Interconnect connectors

Þ

3Ý

Power LED

Þ

4Ý


Þ

5Ý

Service processor error

Before you begin

Before you begin to install options in the server, read the following information:

• Become familiar with the safety and handling guide-

lines provided in “Safety information” on page 196, and

“Handling electrostatic discharge-sensitive devices” on page 199. These guidelines will help you work safely

while working with the server or options.

Installing options

63

• You do not need to turn off the server to install or replace hot-swap power supplies, hot-swap drives, hotswap fans, Active PCI (hot-plug) adapters, or hot-plug

USB devices.

• The orange color on components and labels in the server identifies hot-swap or hot-plug components.

This means that you can install or remove the component while the system is running, provided that the system is configured to support this function.

• The blue color on components and labels identifies touch points where you can grip a component, move a latch, and so on.

• Make sure that you have an adequate number of properly grounded electrical outlets for the server, monitor, and any other options that you intend to install.

• Back up all important data before you make changes to disk drives.

• For a list of supported options for the Netfinity 6000R, refer to http://www.ibm.com/pc/us/compat on the World

Wide Web.

System reliability considerations

To help ensure proper cooling and system reliability, make sure that:

• Each of the drive bays has either a drive or a filler panel installed.

• Each of the power supply bays has either a power supply or a filler panel installed.

• There is at least 50 mm (2 inches) of ventilated space at the sides of the server and 100 mm (4 inches) at the rear of the server.

• The top cover is in place during normal operation.

• The top cover is removed for no longer than 30 minutes while the server is operating.

• The processor housing cover over the processor and memory area is removed for no longer than 10 minutes while the server is operating.

• A removed hot-swap drive is replaced within 10 minutes of removal.

• Cables for optional adapters are routed according to the instructions provided with the adapters.

• A failed fan is replaced within 48 hours.

Working inside the server with the power on

The server supports hot-add, hot-plug and hot-swap devices and is designed to operate safely while turned on with the cover removed. Follow these guidelines when you work inside a server that is turned on:

• Avoid loose-fitting clothing on your forearms. Button long-sleeved shirts before working inside the server; do

64


not wear cuff links while you are working inside the server.

• Do not allow your necktie to hang inside the server.

• Remove jewelry, such as bracelets, necklaces, rings, and loose-fitting wrist watches.

• Remove items from your shirt pocket (such as pens or pencils) that could fall into the server as you lean over it.

• Avoid dropping any metallic objects, such as paper clips, hair pins, or screws, into the server.

Handling static-sensitive devices

Static electricity, though harmless to you, can seriously damage server components or options.

Note: When you are adding an internal option, do not open the static-protective package containing the option until you are instructed to do so.

When you handle options and other server components, take these precautions to avoid damage from static electricity:

• Limit your movement. Movement can cause static electricity to build up around you.

• Always handle components carefully. Handle adapters, the memory board, and memory modules (DIMMs) by the edges. Never touch any exposed circuitry.

• Prevent others from touching components.

• When you are installing a new option, touch the staticprotective package containing the option to a metal expansion-slot screw or other unpainted metal surface on the server for at least two seconds. (This reduces static electricity from the package and from your body.)

• When possible, remove the option and install it directly into the server without setting the option down. When this is not possible, place the static-protective package that the option comes in on a smooth, level surface and place the option on it.

• Do not place the option on the server's covers or any metal surface.

≥

18 kg (37 lbs)

CAUTION:

≥

32 kg (70.5 lbs)

≥

55 kg (121.2 lbs)

Installing options

65

Use safe practices when lifting.

DANGER: Electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard:

• Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm.

• Connect all power cords to a properly wired and grounded electrical outlet.

• Connect to properly wired outlets any equipment that will be attached to this product.

• When possible, use one hand only to connect or disconnect signal cables.

• Never turn on any equipment when there is evidence of fire, water, or structural damage.

• Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures. Connect and disconnect cables as described in the following table when installing, moving, or opening covers on this product or attached devices.

To connect:

1. Turn everything OFF.

2. First, attach all cables to devices.

3. Attach signal cables to connectors.

4. Attach power cords to outlet.

5. Turn device ON.

To disconnect:


2. First, remove power cords from outlet.

3. Remove signal cables from connectors.

4. Remove all cables from devices.

CAUTION:

66


The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

1

2

3

Removing the server top cover and bezel

Review the information in “Before you begin” on page 63.

The following illustration shows how to remove the top cover and bezel from the server.


Þ

1Ý

Top cover

Þ

2Ý

Right release latch

Þ

3Ý

Bezel

Þ

4Ý

Left release latch

Þ

5Ý

Cover release latch

To remove the server top cover:

1. Lift the plastic cover-release latch near the edge of the top cover.

Installing options

67

2. Slide the top cover slightly toward the rear of the server; the cover will stop after about 25 mm (1 inch).

Lift the cover off the server and set the cover aside.

Attention: For proper cooling and airflow, replace the top cover before turning on the server. Operating the server for extended periods of time (over 30 minutes) with the top cover removed might damage server components.

To remove the bezel:

1. Release the two tabs at the top edge of the bezel and pull the top of the bezel slightly away from the server.

2. Pull the bezel up to release the two tabs at the bottom edge of the bezel. Store the bezel in a safe place.

Working with adapters

The following illustration shows the location of the Active™

PCI adapter expansion slots on the system board.

Notes:


2. Active PCI slots are also called hot-plug PCI slots.

Þ

1Ý


Þ

2Ý


Þ

3Ý


Þ

4Ý


Þ

5Ý


Þ

6Ý


68


Þ

7Ý

PCI slot power-on light

Þ

8Ý

PCI slot attention lights

Þ

9Ý


PCI bus configuration

• Hot-plug, 32-bit PCI slot 1 (on PCI bus A, 5V, 33 MHz)

• Hot-plug, 64-bit PCI slots 2 through 4 (on PCI bus B,

3.3V, 66 MHz)

• Hot-plug, 64-bit PCI slots 5 through 6 (on PCI bus C,

5V, 33 MHz)

• Power-on lights for Active PCI slots

• Internal Attention lights for Active PCI slots

• External Attention lights for Active PCI slots

This section gives the procedure for installing a hot-plug PCI adapter. If your operating system supports hot-plug PCI adapters, you can replace a failing hot-plug PCI adapter with a new adapter of the same type without turning off power to the server. If your operating system and adapter also support the hot-add feature, you can install a new adapter without turning off the power to the server.

Before you begin:

•

Review the information in “Before you begin” on page

63 and “Working inside the server with the power on” on page 64.

• Read the documentation that comes with your adapter for any special requirements or restrictions.

• Read the documentation that comes with your operating system.

Attention: Do not remove a hot-plug PCI adapter before performing the operating-system-defined procedure for disabling the Active PCI (hot-plug) slot that contains the adapter. Failure to do so might cause your system to lock up. Refer to your operating-system documentation.

Installing a hot-plug adapter

The following illustration shows how to install a hot-plug PCI adapter.


Installing options

69

Þ

1Ý

Adapter retention latch

Þ

2Ý

Tab

Þ

3Ý

Expansion-slot cover

Þ

4Ý

Power-on light

Þ

5Ý

Adapter

Þ

6Ý

Adapter retention cover

Þ

7Ý

Plastic dividers

To install a hot-plug PCI adapter:

Attention: When you handle Electrostatic Discharge-Sensitive devices (ESD), take precautions to avoid damage from static electricity. For details on handling these devices, refer to the following Web site and search for ESD: http://www.ibm.com

1. Remove the top cover (see “Removing the server top cover and bezel” on page 67).

2. Determine which expansion slot you will use for the adapter.

Note: All six PCI slots support hot-plug PCI adapters.

3. Disable the selected PCI slot from your operating system. (Refer to the documentation that comes with your operating system for information about disabling a hotplug PCI slot.) Disabling the PCI slot turns off the power-on light for that PCI slot.

Attention: Make sure that the power-on light for the hot-plug PCI slot is off before you continue with the next step.

4. Remove the expansion-slot cover: a. Rotate the adapter retention latch counterclockwise.

b. Lift the tab on the top of the expansion-slot cover; then, remove the expansion-slot cover from the server. Store it in a safe place for future use.

70


c. Press on the rear of the adapter retention assembly and lift the adapter retention cover.

Attention: Expansion-slot covers must be installed on all empty slots. This maintains the electromagnetic emissions characteristics of the system and ensures proper cooling of system components.

5. Refer to the documentation that comes with your adapter for any cabling instructions. It might be easier for you to route any cables before you install the adapter.

6. Remove the adapter from the static-protective package.

Attention: Avoid touching the components and goldedge connectors on the adapter.

7. Place the adapter, component-side up, on a flat, staticprotective surface.

8. Install the adapter: a. Carefully grasp the adapter by its top edge or upper corners, and align it with the expansion slot on the system board.

b. Press the adapter

firmly

into the expansion slot.

Attention: When you install an adapter in the server, be sure that it is completely and correctly seated in the system-board connector. Incomplete insertion might cause damage to the system board or the adapter.

c. Lower the tab over the top corner of the adapter.

Rotate the adapter retention latch clockwise until it snaps into place.

9. Connect any needed cables to the adapter.

10. Enable the PCI slot from your operating system. (Refer to the documentation that comes with your operating system for information about enabling a hot-plug PCI slot.) Make sure that the power-on light for the hot-plug

PCI slot comes on.

11. If you have other options to install or remove, do so

now; otherwise, go to “Installing the server top cover and bezel” on page 91.

Cabling example for the ServeRAID adapter

You can install an optional IBM ServeRAID® adapter in the server to control the internal hot-swap hard-disk drives; that is, to enable you to configure the internal hot-swap hard disk drives into disk arrays. To do this, you must turn off the server, disconnect the internal SCSI cable from the integrated SCSI controller on the system board, and connect the cable to a ServeRAID adapter. Refer to the ServeRAID adapter option documentation for complete instructions on installing a ServeRAID adapter in the server. Refer to the

Using IBM ServeRAID

book on the Documentation CD for information on ServeRAID adapters and controllers.

The following procedure describes the cable routing that is necessary when you install a ServeRAID adapter. The following illustrations show the cabling for internal hot-swap

Installing options

71

hard disk drives. You can also cable a ServeRAID adapter to external hard disk drives.

Notes:


2. Refer to the documentation that comes with your adapter for any cabling instructions.

3. Cable identifiers are printed on the cables that come with the server and options. Use these identifiers to connect the cables to the correct connectors. For example, the hard disk drive cables are labeled HDD.

To cable the ServeRAID adapter:

1. Turn off the server.

2. Remove all adapters from the Active PCI adapter slots.

3. Remove the plastic dividers between the PCI adapter slots.

4. Press the fan assembly release latches on both sides of the fan assembly; then, remove the fan assembly from the server.

Þ

1Ý

Plastic dividers

Þ

2Ý

Fan assembly release latch

Þ

3Ý

ServeRAID adapter

5. Disconnect the internal SCSI cable from the SCSI con-

nector (J38) on the system board. (See “System board cable connectors” on page 55).

6. Carefully thread the disconnected end of the internal

SCSI cable out of the chassis, pulling the cable out of the opening in the chassis.

7. Reinstall the fan assembly in the server.

72


8. Replace the plastic dividers between the PCI adapter slots.

9. Reinstall the adapters in the PCI adapter slots.

10. The following illustration shows how to route the SCSI cable to the ServeRAID adapter.

Attention: When you route the SCSI cable, observe the following:

• Do not block the ventilated space in front of the fan assembly.

• Do not place the SCSI cable fold on top of the fan assembly.

• Do not route the SCSI cable over the memory board assembly.

ServeRAID adapter

CPU

Memory

PCI

Bus A B C D

Power

Supply 1 2 3 4

Fan

DASD

NMI

SP Bus

Event Log

Non Red

Over Spec

Temp

11. Install the ServeRAID adapter in the desired PCI slot.

See “Installing a hot-plug adapter” on page 69 for

adapter installation instructions. Refer to the ServeRAID adapter option documentation for additional information on installing a ServeRAID adapter in the

Installing options

73

server and connecting the SCSI cable to a ServeRAID adapter.

12. Connect the SCSI cable to an internal channel connector on the ServeRAID adapter.

Note: Refer to the

Using IBM ServeRAID

book on the

Documentation CD for information on ServeRAID adapters and controllers.

Installing internal drives

If you add different types of drives, the system can read multiple types of media and store more data. Several types of drives are available, such as:

• Diskette

• Hard disk

• CD-ROM

• DVD-ROM

• Tape

Note: The server supports external tape drives; however, the server does not support internal tape drives.

The server contains hardware that enables you to replace a failed hard disk drive without turning off the server. Therefore, you have the advantage of continuing to operate the system while a hard disk drive is removed or installed.

These drives are known as

hot-swap

drives.

Each hot-swap drive bay has two indicator lights on the front

of the server (see “Start the server” on page 8). If the amber

hard-disk status light for a drive is lit continuously, that individual drive is faulty and requires replacement. When the hard-disk status light indicates a drive fault, you can replace a hot-swap drive without turning off the server.

Each hot-swap drive that you plan to install must be mounted in a hot-swap-drive tray. The drive must have a single connector attachment (SCA) connector. Hot-swapdrive trays come with hot-swap drives.

Internal drive bays

Internal drives are installed in

bays

. The server supports up to a maximum of six 1-inch (26 mm) slim high, 3.5 inch, hotswap hard disk drives when the media bay option is installed.

74


Þ

1Ý

CD-ROM drive

Þ

2Ý

Diskette drive

Þ

3Ý

Hot-swap bays (up to six)

Þ

4Ý

Optional hard disk drives

Þ

5Ý

Standard hard disk drives

3.5-inch diskette drive

CD-ROM drive

3 hot-swap hard disk drives

• The server comes with one integrated drive electronics

(IDE) CD-ROM drive and one 3.5-inch, 1.44 MB diskette drive.

• The CD-ROM drive bay (bottom left front) supports

5.25-inch, half-high, removable-media drives. However, you cannot install additional removable-media drives in the server.

• The server supports three standard and three optional

1-inch (26 mm) slim-high, 3.5-inch, hot-swap hard disk drives in the hot-swap bays. The standard hot-swap bays are bays 1 through 3 (from bottom to top). The optional hot-swap bays are bays 4 through 6 (from bottom to top). Bays 1 through 3 are located in the standard hard disk drive cage, to the left of bays 4 through

6 in the optional hard disk drive cage.

Note: The server does not support half-high hot-swap drives or internal tape drives.

• The hot-swap bays connect to a hot-swap drive

backplane

. The backplane is a printed circuit board behind the bays.

Hard disk drive component locations

The following illustration shows the hot-swap-drive backplane component locations, as viewed from the front of the server.


Installing options

75

Þ

1Ý

Hard disk drive activity light (green)

Þ

2Ý

Hard disk drive status light (amber)

Þ

3Ý

SCSI hot-swap hard disk drive connector

Note: The hard-disk drive activity light and hard-disk drive status light on the backplane match the hard-disk drive activity light and hard-disk drive status light on

the front of the server (see “Start the server” on page

8).

The following illustration shows the rear connectors on the hot-swap-drive backplane before the repeater card is installed, as viewed from the rear of the server.

Þ

1Ý

SCSI cable connector

Þ

2Ý

SCSI power cable connector

Þ

3Ý

I2C cable connector

Note: To install an additional hot-swap drive backplane on

the back of the server, see “Installing a Netfinity 3-

Pack Ultra160 Hot-Swap Expansion Kit” on page 87.

Installing a hot-swap hard disk drive

The following illustration shows how to install a hot-swap hard disk drive.

Note: You do not have to turn off the server to install hotswap drives in these bays.

76


Þ

1Ý

Filler panel

Þ

2Ý

Drive tray assembly

Þ

3Ý

Drive tray handle (open position)

To install a drive in a hot-swap bay:

1. Review “Before you begin” on page 63.

2. Unlock and open the server front door.

Attention:

To maintain proper system cooling, do not operate the server for more than 10 minutes without either a drive or a filler panel installed for each bay.

3. Remove the filler panel from one of the empty hot-swap bays by inserting your finger into the depression at the left side of the filler panel and pulling it away from the server.

4. Install the hard disk drive in the hot-swap bay: a. Ensure that the tray handle is open (that is, perpendicular to the drive).

b. Align the drive assembly so that it engages the guide rails in the bay.

c. Gently push the drive assembly into the bay until the drive stops.

d. Push the tray handle to the closed (locked) position.

e. Check the hard disk drive status indicator to verify that the hard disk drive is operating properly.

If the amber hard-disk status light for a drive is lit continuously, that individual drive is faulty and needs to be replaced. If the green hard-disk activity light is flashing, the drive is being accessed.

Note: If the server has a ServeRAID controller or adapter installed, you might need to reconfigure the disk arrays after installing hard disk drives.

Refer to

Using IBM ServeRAID

on the Documentation CD or the Hardware Maintenance

Manual pertaining to the specific RAID adapter for information.

Installing options

77

Installing memory-module kits

The illustrations in this document might differ slightly from your hardware.

Adding memory to the server is an easy way to make programs run faster. You can increase the amount of memory in the server by installing memory-module options. You must install a bank of four matched dual-inline memory modules (DIMMs).

Notes:

1. The DIMM options available for the server are 128 MB,

256 MB, 512MB, and 1 GB. The server supports a minimum of 512 MB (4 x 128MB) and a maximum of 16 GB

(16 x 1GB) of system memory.

2. When 4 GB of memory is installed in the server, the amount of usable memory will be reduced depending on the system configuration. A certain amount of memory must be reserved below 4 GB for system resources. A second reduction in the usable memory is made when 16 GB of memory is installed.

3. The server comes with a minimum of 512 MB (4x128) memory installed in bank 1. When you install additional

DIMMs, be sure to follow the DIMM population

sequence in Table 11 on page 79.

4. All the DIMMs installed in a bank must be the same size, speed, type, and technology. You can mix compatible DIMMs from various manufacturers.

5. All the banks do not have to contain DIMMs of the same size, speed, type, and technology. You can mix compatible DIMMs from various manufacturers.

6. The memory board contains 16 DIMM connectors and

utilizes 4-way memory interleaving. See Table 11 on page 79.

The 4-way memory interleave technology in the server requires that you install DIMMs in all four connectors in each populated bank.

7. Install only 3.3 V, 168-pin, 8-byte, 100 MHz, PCI,

PC100-322-622R, registered synchronous dynamic random-access memory (SDRAM) with error correcting code (ECC), DIMMs. Only 100MHz, 72-bit, registered, synchronous, x4 SDRAM configuration DIMM memory is supported for the 128MB, 256 MB, 512 MB, and 1GB

DIMMs.

8. Installing or removing DIMMs changes the configuration information in the server. Therefore, after installing or removing a bank of DIMMs, you must save the new configuration information using the Configuration/Setup

Utility program. When you restart the server, the system displays a message indicating that the memory configuration has changed. Start the Configuration/Setup Utility program and select Save Settings.

See “Configuring the server” on page 43 for more infor-

mation.

Install the DIMMs in the order provided in Table 11 on page

79.

78


Bank of 4 DIMMs Install DIMMs in these connectors:

Bank 1 (shipped as standard) J1, J5, J9, J13

Bank 2 J2, J6, J10, J14

Bank 3

Bank 4

J3, J7, J11, J15

J4, J8, J12, J16

Table 11. DIMM installation order

The following illustration shows how to install memory on the memory board.


Þ

1Ý

Memory slot 1

Þ

2Ý

Memory slot 9

Þ

3Ý

Error LEDs

Þ

4Ý

Memory slot 13

Þ

5Ý

Error LEDs

Þ

6Ý

Memory slot 5

Before you begin:

•

Review “Before you begin” on page 63.

• Read the documentation that comes with your option.

To install a DIMM:

Attention: When you handle Electrostatic Discharge-Sensitive devices (ESD), take precautions to avoid damage from static electricity. For details on handling these devices, refer

Installing options

79

to the following Web site and search for ESD: http://www.ibm.com

1. Turn off the server and disconnect all power cords and external cables; then, remove the top cover (see

“Removing the server top cover and bezel” on page

67).

2. Remove the memory board assembly: a. Lift up on the memory board assembly and remove it from the server.

Memory board b. Place the memory board assembly on a staticprotective surface, such as the static-protective package in which an option comes.

3. Locate the DIMM connectors on the memory board.

Determine the DIMM connectors into which you will install the DIMMs. (See the notes at the beginning of this procedure.)

4. Touch the static-protective package that contains the

DIMM option to any unpainted metal surface on the server. Then, remove the DIMM from the package.

Note: To avoid breaking the retaining clips or damaging the DIMM connectors, handle the clips gently.

5. To install the DIMMs, repeat the following steps for each DIMM that you install: a. Turn the DIMM so that the DIMM keys align correctly with the connector.

b. Insert the DIMM by pressing the DIMM straight into the connector. Be sure that the retaining clips snap into the closed positions.

c. Make sure that the retaining clips are in the closed position. If a gap exists between the DIMM and the retaining clips, the DIMM has not been properly installed. In this case, open the retaining clips and remove the DIMM; then, reinsert the DIMM.

6. Install the memory board assembly:

80


a. Hold the memory board assembly, and align it into the card guides and over the memory board connector.

Attention: When you insert the memory board assembly into the connector, press on the flat metal projection on the board.

b. Insert the memory board assembly into the connector.



Installing a microprocessor kit

The server comes with one microprocessor installed on the system board. The server supports up to four microprocessors. If you install at least one additional microprocessor, the server can operate as a symmetric multiprocessing

(SMP) server. With SMP, certain operating systems and application programs can distribute the processing load among the microprocessors.

Before you begin:

•


63.

• Thoroughly review the documentation that comes with the microprocessor, so that you can determine whether you need to update the server basic input/output system (BIOS). The latest level of BIOS for the server is available through the World Wide Web and the IBM

Bulletin Board System (BBS). Go to http://www.pc.ibm.com/support/, select IBM Servers, and make the selections for the server.

• Obtain an SMP-capable operating system (optional).

For a list of supported operating systems, see http://www.ibm.com/pc/us/compat/ on the World Wide

Web.

Attention: To avoid damage and ensure proper server operation when you install a new or an additional microprocessor, use microprocessors that have the same cache size and type, and the same clock speed. Microprocessor internal and external clock frequencies must be identical.

Notes:

1. To order additional microprocessor options, contact your IBM reseller or IBM marketing representative.

2. The server comes standard with one microprocessor installed in microprocessor connector J34 (slot 1) on the system board, and a terminator card in microprocessor slot 4. The microprocessor in slot 1 is the startup (boot) microprocessor. The microprocessor installed in microprocessor connector J35 is microprocessor 2 (slot 2); the microprocessor installed in microprocessor connector J36 is microprocessor 3 (slot 3); and the microprocessor installed in microprocessor connector J37 is microprocessor 4 (slot 4). If more than one microprocessor is installed, the highest num-

Installing options

81

bered microprocessor is the microprocessor from which the server will start. The lower numbered microprocessors are used as application microprocessors.

3. If you replace the microprocessors in the server with microprocessors of a different speed, be sure to set the microprocessor-core-frequency-selection jumper block correctly, as described in this section. For a list of supported microprocessor speeds, see http://www.ibm.com on the World Wide Web.


If you need to install additional microprocessors, install them in the following order:

• Slot 1 (first slot, connector J34)

• Slot 2 (second slot, connector J35)

• Slot 3 (third slot, connector J36)

• Slot 4 (fourth slot, connector J37)

Attention: The server comes with a terminator card installed in microprocessor slot 4. To ensure proper server operation, the terminator card must remain installed in microprocessor slot 4 until you have installed microprocessors in slots 1 through 3.

The following illustration is a simplified layout of the microprocessor connector locations and other microprocessorrelated components on the system board.


82


Þ

1Ý


Þ

2Ý


Þ

3Ý


Þ

4Ý


Þ

5Ý

Memory board (J40)

Þ

6Ý


Þ

7Ý


Þ

8Ý


Þ

9Ý


Þ

10Ý


Þ

11Ý


Þ

12Ý


Þ

13Ý

Battery

Note: For additional illustrations of the system-board com-

ponents, see “System board component locations” on page 54.

The following illustration shows how to install a microprocessor on the system board.


Terminator card

Latch

Microprocessor

Latch

To install an additional microprocessor:


Installing options

83

Note: If you are replacing a failed microprocessor, verify that you have selected the correct microprocessor for replacement. To do this, check the Diagnostic panel that is located under the top cover to see which LED is on.

1. Turn off the server and disconnect all power cords and external cables; then, remove the top cover (see

“Removing the server top cover and bezel” on page

67).

2. Determine the slot where the microprocessor is to be installed.

3. If you have installed microprocessors in slots 1 through

3 and you are now installing a microprocessor in slot 4, remove the terminator card from the microprocessor connector. Store the terminator card in a safe place in the static-protective package that your new microprocessor comes in; you will need to install it again if you ever remove the microprocessor.

4. Install the microprocessor: a. Touch the static-protective package containing the new microprocessor to any

unpainted

metal surface on the server; then, remove the microprocessor from the package.

b. Hold the microprocessor by the open latches, and center the microprocessor over the microprocessor connector.

Attention: Make sure that the microprocessor is oriented and aligned correctly before you try to close the latches.

c. Carefully close the latches to seat the microprocessor in the connector.

5. If you replace the microprocessors in the server with microprocessors of a different speed, set the microprocessor-core-frequency-selection jumper block as

described in Table 12. To ensure that the server main-

tains the correct microprocessor bus-to-core ratio, you must set the following microprocessor speed (core-frequency-selection) jumpers: J13, J27, J28, and J29.

The jumpers on this block are in the following order, from top to bottom: J13, J27, J28, and J29. For loca-

tions of these jumpers, see “System board jumpers” on page 56.

Note: See “Changing jumper positions” on page 85 for

additional information on setting jumpers.

J13 J27 J28 J29

Bus

Ratio

7:1

Core

Frequency

(MHz)

700/100 H L L H

Table 12. Microprocessor-core-frequency-selection jumper block settings



84


Changing jumper positions

Jumpers located on the system board help you to customize the way the server operates.

The server system board contains two-pin and three-pin jumper blocks.

In some cases, groups of jumpers might combine to define a function.

Three-pin jumper blocks

With the three-pin jumper blocks, each jumper covers two of the three pins on a pin block. You can position the jumper to fit over the center pin and either of the other two pins.

The following illustration identifies pins 1, 2, and 3 on a three-pin jumper block.

3

2 1

To change a jumper position for a three-pin jumper block:

1. Turn off the server; then, disconnect all power cords and external cables.

2. Remove the server cover (see “Removing the server top cover and bezel” on page 67).

3. Lift the jumper straight off the pin block.

4. Align the holes in the bottom of the jumper with the center pin and the pin that was not covered previously.

5. Slide the jumper fully onto these pins.

6. Reinstall the server cover and connect the cables (see

“Installing the server top cover and bezel” on page 91).

Installing a hot-swap power supply

The following illustration shows how to install a hot-swap power supply.

Installing options

85


Þ

1Ý

Filler panel

Þ

2Ý

AC power light

Þ

3Ý

DC power light

Þ

4Ý

Power supply handle

Þ

5Ý

Power supply

To install an additional power supply:

1. Remove the filler panel.

2. Place the handle on the power supply in the open position.

3. Slide the power supply into the chassis and close the handle.

4. Plug the power cord into the power supply; then, into a properly grounded electrical outlet.

5. Verify that the DC Power light and the AC Power light on the power supply are lit, indicating that the power supply is operating properly.

CAUTION:

86


Never remove the cover on a power supply or any part that has the following label attached.

Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components. If you suspect a problem with one of these parts, contact a service technician.

CAUTION:

If you install a strain-relief bracket option over the end of the power cord that is connected to the device, you must connect the other end of the power cord to an easily accessible power source.

Installing a Netfinity 3-Pack Ultra160 Hot-

Swap Expansion Kit

You can install an optional Netfinity 3-Pack Ultra160 Hot-

Swap Expansion Kit in the server to connect three additional hot-swap hard disk drives to the server. This kit contains a hot-swap hard disk drive backplane that you install adjacent to the standard hot-swap hard disk drive backplane. The server supports a maximum of two hot-swap drive backplanes.

Notes:

1. In addition to the optional hot-swap drive backplane, the Netfinity 3-Pack Ultra160 Hot-Swap Expansion Kit comes with a hard disk drive cage. Do not install the hard disk drive cage on the server, as the hard disk drive cage is not compatible with the Netfinity 6000R server. The Netfinity 3-Pack Ultra160 Hot-Swap

Expansion Kit can be installed in various types of Netfinity servers; the hard disk drive cage is used with other types of servers.

2. Cable identifiers are printed on the cables that come with the server and options. Use these identifiers to connect the cables to the correct connectors. For example, the hard disk drive cables are labelled HDD.

Installing options

87

3. For information on cabling options and using the Netfinity 3-Pack Ultra160 Hot-Swap Expansion option, refer to the documentation that comes with the option kit.

4. For additional information on cabling, see “Cabling example for the ServeRAID adapter” on page 71 and

“Cabling the server” on page 107.

5. The hot-swap drive backplane components are shown

at “Installing a hot-swap hard disk drive” on page 76.

Note: The hard-disk drive activity light and hard-disk drive status light on the backplane match the hard-disk drive activity light and hard-disk drive status light on

the front of the server (see “Start the server” on page

8).

The rear connectors on the hot-swap-drive backplane

(before repeater card is installed) can be seen at “Installing a hot-swap hard disk drive” on page 76.

The following illustration shows the rear connectors on the

SCSI repeater card after the repeater card is installed, as viewed from the rear of the server.

Þ

1Ý

SCSI power cable connector

Þ

2Ý

I2C cable connector

Þ

3Ý

SCSI repeater card cable connector

Þ

4Ý

SCSI cable connector

The following illustration shows how to install a Netfinity 3-

Pack Ultra160 Hot-Swap Expansion Kit.

88


Expansion backplane

To install a Netfinity 3-Pack Ultra160 Hot-Swap Expansion

Kit:


1. Review the information in “Before you begin” on page

63 and in “Safety information” on page 196.

2. Turn off the server and peripheral devices and disconnect all power cords and external cables; then, remove

the top cover (see “Removing the server top cover and bezel” on page 67).

3. Refer to the documentation that comes with the option to assemble the hot-swap expansion option.

4. Align the hot-swap expansion option with the empty slot at the rear of the optional hard disk drive cage, adjacent to the standard hot-swap hard disk drive backplane.

5. Slide the hot-swap expansion option down into the guides on the slot at the rear of the optional hard disk drive cage, and secure it to the server with the blue slide latch located on top of the optional hard disk drive cage.

6. Refer to the documentation that comes with the option to complete the installation of the option.

7. Install additional internal hot-swap hard disk drives in

the optional hard disk drive cage (see “Installing a hotswap hard disk drive” on page 76), and connect the

drives to the optional hot-swap backplane. You can connect a maximum of three hot-swap hard disk drives to the optional hot-swap backplane.

Note: If you connected these optional hot-swap hard disk drives to the optional hot-swap backplane, then the optional hot-swap backplane sets the

SCSI IDs for the optional hot-swap backplane

and the hot-swap hard disk drives. See “Setting

SCSI IDs” on page 97 for additional information.



Installing options

89

Replacing a hot-swap fan

The server comes with six hot-swap fans. You do not need to turn off the power to the server to replace a hot-swap fan assembly.

Attention:

To help ensure proper cooling, replace a fan that has failed within 48 hours.

Note: The speed of the fans will increase if:

• One fan fails.

• Ambient temperature gets too high.

The following illustration shows how to replace hot-swap fans.


Hot-swap fans

To replace a hot-swap fan assembly:


Attention:

To ensure proper system cooling, do not remove the top cover for more than 30 minutes during this procedure.

2. Lift the fan release handle and lift the fan out of the server.

3. Slide the replacement fan into the server and press the handle down.

4. Replace the top cover (see “Installing the server top cover and bezel” on page 91).

90


Completing the installation

To complete the installation, you must reinstall the top cover, reinstall the bezel, reconnect all cables that you disconnected, and, for certain options, run the Configuration/Setup

Utility program. Follow the instructions in this section.

Attention:

For correct cooling and airflow, install the top cover before turning on the server. Operating the server for extended periods of time (over

30 minutes) with the top cover removed might damage server components.

To complete the installation, you must reinstall the top cover, reinstall the media-bay bezel, reconnect all the cables that you disconnected earlier and, for certain options, run the

Configuration/Setup Utility program. Follow the instructions in this section.

Attention:

For correct cooling and airflow, install the top cover before turning on the server. Operating the server for extended periods of time (over

30 minutes) with the top cover removed might damage server components.

Note: If you have just plugged the power cords of the server into an electrical outlet, you will have to wait approximately 20 seconds before pressing the power-control button.

Installing the server top cover and bezel

The following illustration shows how install the server top cover.


Þ

1Ý

Top cover

Þ

2Ý

Right release latch

Þ

3Ý

Bezel

Þ

4Ý

Left release latch

Þ

5Ý

Cover release latch

Installing options

91

To install the server top cover:

1. Before installing the cover, check that all cables, adapters, and other components are installed and seated correctly and that you have not left loose tools or parts inside the server.

2. Place the cover-release latch in the open (up) position.

3. Insert the bottom tabs of the top cover in the matching slots in the server chassis.

4. Close the cover-release latch to pull the top cover forward and lock the top cover in place.

5. If you disconnected any cables from the back of the server, reconnect the cables; then, plug the power cords into properly grounded electrical outlets.

Note: If necessary, refer to “Input/Output ports” on page 93 for connector locations.

To install the bezel:

1. Insert the two tabs on the bottom of the bezel into the matching holes on the server chassis.

2. Push the top of the bezel toward the server until the two tabs at the top of the bezel snap into place.

Updating the server configuration

When you start the server for the first time after you add or remove an internal option or an external SCSI device, you might see a message telling you that the configuration has changed. The Configuration/Setup Utility program automatically starts so that you can save the new configuration infor-

mation. See “Configuring the server” on page 43.

Some options have device drivers that you need to install.

Refer to the documentation that comes with your option for information about installing any required device drivers.

The server comes with at least one microprocessor installed on the system board. If you have installed one or more additional microprocessors, the server can now operate as an

SMP server. Therefore, you might need to upgrade your operating system to support SMP.

If the server has a ServeRAID adapter installed and you have installed or removed a hard disk drive, refer to the documentation that comes with your ServeRAID adapter for information about reconfiguring your disk arrays.

Connecting external options

Before you begin:

•

Review “Before you begin” on page 63.

• Read the documentation that comes with your options.

You can attach external options to the input/output (I/O) con-

nectors on the rear of the server. (See “Input/Output ports” on page 93 for more information.)

To attach an external device:

92


1. Turn off the server and all attached devices.

2. Follow the instructions that come with the option to prepare it for installation and to connect it to the server.

Note: If you are attaching an external SCSI device, see

“Ultra160 SCSI ports” on page 97 for information

about SCSI cabling and SCSI IDs.

Input/Output ports

This section provides information about the input/output

(I/O) ports on the rear of the server. These ports include the following:

• One parallel port

• One video port

• One keyboard port

• One auxiliary-device port (pointing device) port

• Two Ultra160 SCSI ports

• Two serial ports

• Two Universal Serial bus (USB) ports

• One Ethernet port

• Three communication ports dedicated to the Netfinity

Advanced System Management processor

The following illustration shows the I/O port connectors on the rear of the server.


Þ

1Ý

Advanced System Management Interconnect port A

Þ

2Ý

Advanced System Management Interconnect port B

Þ

3Ý

Video

Þ

4Ý

Management port C

Þ

5Ý

USB 1

Þ

6Ý

USB 2

Þ

7Ý

Ethernet

Þ

8Ý

Parallel

Þ

9Ý

Serial B

Installing options

93

Þ

10Ý

Serial A

Þ

11Ý

Keyboard

Þ

12Ý

Mouse

Parallel port

The server has one parallel port. This port supports three standard Institute of Electrical and Electronics Engineers

(IEEE) 1284 modes of operation: Standard Parallel Port

(SPP), Enhanced Parallel Port (EPP), and Extended Capability Port (ECP).

Viewing or changing the parallel-port assignments

You can use the built-in Configuration/Setup Utility program to configure the parallel port as bidirectional; that is, so that data can be both read from and written to a device. In bidirectional mode, the server supports the ECP and EPP modes.

To view or change the parallel-port assignment:

1. Restart the server and watch the monitor screen.

2. When the message

Press F1 for Configuration/Setup appears, press F1.

Note: The Devices and I/O Ports choice appears only on the full configuration menu. If you set two levels of passwords, you must enter the administrator password to access the full configuration menu.

3. From the main menu, select Devices and I/O Ports; then, press Enter.

4. Select the parallel port; then, use the arrow keys to advance through the settings available.

Note: When you configure the parallel port as bidirectional, use an IEEE 1284-compliant cable. The maximum length of the cable must not exceed 3 meters (9.8 feet).

5. Select Save Settings; then, select Exit Setup to exit from the Configuration/Setup Utility main menu.

Parallel port connector

The following table shows the pin-number assignments for the 25-pin, female D-shell parallel-port connector on the rear of the server.

13

1

25 14

Table 13. Parallel-port connector pin-number assignments

Pin

1

2

I/O

O

I/O

SPP/ECP Signal

-STROBE

Data 0

EPP Signal

-WRITE

Data 0

94


Table 13. Parallel-port connector pin-number assignments

I

O

I

O

I/O

I

I

I

I/O

I/O

I/O

I/O

I/O

I/O

I/O

—

—

—

—

—

O

—

—

—

13

14

15

16

9

10

11

12

Pin

3

4

7

8

5

6

21

22

23

24

25

17

18

19

20

SPP/ECP Signal

Data 1

Data 2

Data 3

Data 4

Data 5

Data 6

EPP Signal

Data 1

Data 2

Data 3

Data 4

Data 5

Data 6

Data 7

-ACK

BUSY

PE (paper end)

Data 7

-ACK

-WAIT

PE (paper end)

SLCT (select) SLCT (select)

-AUTO FD (feed) -AUTO FD

-ERROR

-INIT

-ERROR

-INIT

-SLCT IN

Ground

Ground

Ground

Ground

Ground

Ground

Ground

Ground

-SLCT IN

Ground

Ground

Ground

Ground

Ground

Ground

Ground

Ground

Video port

The server comes with an integrated super video graphics array (SVGA) video controller. This controller is not removable, but you can disable it by installing a PCI video adapter.

Note: If you install a PCI video adapter, the server BIOS will automatically disable the integrated video controller.

The following table shows the pin-number assignments for the 15-pin analog video connector on the rear of the server.

5 1

15 11

Table 14. Video-port connector pin-number assignments

Pin

1 Red

2 Green or monochrome

3 Blue

Signal

4 Monitor ID bit 2

5 Ground

6 Ground

7 Ground

8 Ground

Installing options

95

Table 14. Video-port connector pin-number assignments

Pin

9 +5 V dc

10 Ground

Signal

11 Monitor ID bit 0

12 DDC SDA

13 Horizontal synchronization (Hsynch)

14 Vertical synchronization (Vsynch)

15 DDC SCL

Keyboard port

There is one keyboard connector on the rear of the server.

Note: If you attach a standard (non-USB) keyboard to the keyboard connector, the USB ports and devices will be disabled during the power-on self-test (POST).

The following table shows the pin-number assignments for the keyboard connector on the rear of the server.

6

4

2

1

5

3

Table 15. Keyboard connector pin-number assignments

Pin

1

2

3

4

5

6

I/O

I/O Data

N/A Reserved

N/A Ground

N/A +5 V dc

I/O Keyboard clock

N/A Reserved

Signal

Auxiliary-device (pointing device) port

The system board has one auxiliary-device port that supports a mouse or other pointing device.

The following table shows the pin-number assignments for the auxiliary-device connector on the rear of the server.

6

4

2

1

5

3

96


Table 16. Auxiliary-device connector pin-number assignments

Signal Pin

1

2

3

4

5

6

Data

Not connected

Ground

+5 V dc

Clock

Not connected

Ultra160 SCSI ports

The server has an integrated dual-channel Ultra160 small computer system interface (SCSI) controller. This controller supports two independent Ultra 160/m SCSI channels: one internal and one external. Each of these channels supports up to 15 SCSI devices. In addition, this controller uses:

• Double-transition clocking to achieve high transfer rates

• Domain name validation to negotiate compatible data transfer speeds with each device

• Cyclic-redundancy checking (CRC), instead of the usual parity checking, to significantly improve data reliability

• An active terminator on the system board for SCSI bus termination

The server comes with two SCSI cables. One cable connects the internal SCSI channel connector to the standard hot-swap-drive backplane. The other cable is not connected to the server when the server is shipped and must be installed in the server. If you want to use the external LVD

SCSI channel connector to connect external SCSI devices to the server, remove the knockout on the rear of the server and install the LVD SCSI cable that comes with the server.

Note: If you install a PCI RAID adapter to configure and manage the internal hot-swap drives, you must move the SCSI cable from the system-board SCSI connector to an internal channel connector on the RAID

adapter. See “Cabling example for the ServeRAID adapter” on page 71 for additional information.

SCSI cabling requirements

If you plan to attach external SCSI devices, you must order additional SCSI cables. To select and order the correct cables for use with external devices, contact your IBM reseller or IBM marketing representative.

For information about the maximum length of SCSI cable between the terminated ends of the cable, refer to the ANSI

SCSI standards. Adhering to these standards will help ensure that the server operates properly.

Setting SCSI IDs

Each SCSI device connected to a SCSI controller must have a unique SCSI ID. This ID enables the SCSI controller to identify the device and ensure that different devices on the

Installing options

97

same SCSI channel do not attempt to transfer data simultaneously. SCSI devices that are connected to different SCSI channels can have duplicate SCSI IDs. The following table lists the SCSI IDs for devices that are connected to one channel. Note that the hot-swap hard disk drive bay numbers are from bottom to top.

Standard Optional

Drive bay 1: SCSI ID 0 Drive bay 4: SCSI ID 12



Backplane: SCSI ID 8 Backplane: SCSI ID 9

Table 17. SCSI IDs for hot-swap hard disk drives and backplanes

The hot-swap-drive backplane controls the SCSI IDs for the internal hot-swap drive bays. However, when you attach a

SCSI device to the external SCSI connector, you must set a unique ID for the device. Refer to the information that is provided with the device for instructions to set its SCSI ID.

SCSI connector pin-number assignments

The following table shows the pin-number assignments for the 68-pin SCSI connectors.

34

1

68 35

Pin Signal

1 +Data 12

2 +Data 13

3 +Data 14

4 +Data 15

5 +Data P1

6 +Data 0

7 +Data1

8 +Data 2

9 +Data 3

10 +Data 4

11 +Data 5

12 +Data 6

13 +Data 7

14 +Data P

15 Ground

16 DIFFSENS

17 Term power

18 Term power

19 Reserved

Pin Signal

35 -Data 12

36 -Data 13

37 -Data 14

38 -Data 15

39 -Data P1

40 -Data 0

41 -Data 1

42 -Data 2

43 -Data 3

44 -Data 4

45 -Data 5

46 -Data 6

47 -Data 7

48 -Data P

49 Ground

50 Ground

51 Term power

52 Term power

53 Reserved

Table 18. 68-pin SCSI connector pin-number assignments

98


Pin Signal

20 Ground

21 +Attention

22 Ground

23 +Busy

24 +Acknowledge

25 +Reset

26 +Message

27 +Select

28 +Control/Data

29 +Request

30 +Input/Output

31 +Data 8

32 +Data 9

33 +Data 10

34 +Data 11

Pin Signal

54 Ground

55 -Attention

56 Ground

57 -Busy

58 -Acknowledge

59 -Reset

60 -Message

61 -Select

62 -Control/Data

63 -Request

64 -Input/Output

65 -Data 8

66 -Data9

67 -Data 10

68 -Data 11

Table 18. 68-pin SCSI connector pin-number assignments

Serial ports

The server has two standard serial ports: Serial port A and

Serial port B. The operating system can use and share both serial ports; however, the integrated Netfinity Advanced System Management processor can use and share only Serial port A.

Some application programs require specific ports, and some modems function properly only at certain communication port addresses. You might need to use the Configuration/Setup Utility program to change communication port address assignments to prevent or resolve address conflicts.

Viewing or changing the serial-port assignments

To view or change the serial-port assignments:

1. Restart the server and watch the monitor screen.

2. When the message

Press F1 for Configuration/Setup appears, press F1.

3. From the main menu, select Devices and I/O Ports; then, press Enter.

Note: The Devices and I/O Ports choice appears only on the full configuration menu. If you set two levels of passwords, you must enter the administrator password to access the full configuration menu.

4. Select the serial port; then, use the arrow keys to advance through the settings available.

5. Select Save Settings; then, select Exit Setup to exit from the Configuration/Setup Utility main menu.

Serial-port connectors

The following table shows the pin-number assignments for the 9-pin, male D-shell serial-port connectors on the rear of the server. These pin-number assignments conform to the industry standard.

Installing options

99

1

6 9

5

Pin Signal

1 Data carrier detect

2 Receive data

3 Transmit data

4 Data terminal ready

5 Signal ground

Pin Signal

6 Data set ready

7 Request to send

8 Clear to send

9 Ring indicator

Table 19. Serial-port connectors pin-number assignments

Universal Serial Bus ports

The server has two Universal Serial Bus (USB) ports, which configure automatically. USB is an emerging serial interface standard for telephony and multimedia devices. It uses Plug and Play technology to determine the type of device attached to the connector.

Notes:

1. If you attach a standard (non-USB) keyboard to the keyboard connector, the USB ports and devices will be disabled during the power-on self-test (POST).

2. If you install a USB keyboard that has a mouse port, the USB keyboard emulates a mouse and you will not be able to disable the mouse settings in the Configuration/Setup Utility program.

USB cables and hubs

You need a 4-pin cable to connect devices to USB 1 or USB

2. If you plan to attach more than two USB devices, you must use a hub to connect the devices. The hub provides multiple connectors for attaching additional external USB devices.

USB technology provides up to 12 megabits-per-second

(Mbps) speed with a maximum of 127 external devices and a maximum signal distance of five meters (16 ft.) per segment.

USB-port connectors

Each USB port has an external connector on the rear of the server for attaching USB compatible devices.

The following table shows the pin-number assignments for the USB-port connectors on the rear of the server.

Pin

1

2

3

VCC

-Data

+Data

Signal

Table 20. USB-port connector pin-number assignments

100


Pin

4 Ground

Signal

Table 20. USB-port connector pin-number assignments

Ethernet port

The server comes with an integrated Ethernet controller.

This controller provides an interface for connecting to 10-

Mbps or 100-Mbps networks and provides full-duplex (FDX) capability, which enables simultaneous transmission and reception of data on the Ethernet local area network (LAN).

To access the Ethernet port, connect a Category 3, 4 or 5 unshielded twisted-pair (UTP) cable to the RJ-45 connector on the rear of the server.

Note: The 100BASE-TX Fast Ethernet standard requires that the cabling in the network be Category 5 or higher.

The Ethernet (RJ-45) connector has two lights. The Ethernet link-status light is on the left. When this green light is on, there is an active connection on the Ethernet port. The

Ethernet transmit/receive activity light on the right. When this amber light is on, there is activity between the server and the network. These lights have the same functions as the Ethernet link-status light and the Ethernet trans-

mit/receive activity light on the information panel (see “Information LED panel” on page 10).

Configuring the Ethernet controller

When you connect the server to the network, the Ethernet controller automatically detects the data-transfer rate

(10Mbps or 100Mbps) on the network and then sets the controller to operate at the appropriate rate. That is, the

Ethernet controller will adjust to the network data rate, whether the data rate is standard Ethernet (10BASE-T), Fast

Ethernet (100BASE-TX), half duplex (HDX), or full duplex

(FDX). The controller supports half-duplex (HDX) and fullduplex (FDX) modes at both speeds.

The Ethernet controller is a PCI Plug and Play device. You do not need to set any jumpers or configure the controller for your operating system before you use the Ethernet controller. However, you must install a device driver to enable your operating system to address the Ethernet controller. The device drivers are provided on the ServerGuide CDs.

Failover for redundant Ethernet

The IBM Netfinity 10/100 Fault Tolerant Adapter is an optional redundant network interface card (NIC adapter) that you can install in the server. If you install this NIC adapter and connect it to the same logical LAN segment as the primary Ethernet controller, you can configure the server to support a

failover

function. You can configure either the integrated Ethernet controller or the NIC adapter as the primary Ethernet controller. In failover mode, if the primary

Ethernet controller detects a link failure, all Ethernet traffic associated with it is switched to the redundant (secondary) controller. If the appropriate device drivers are installed, this switching occurs without any user intervention. When the primary link is restored to an operational state, the Ether-

Installing options

101

net traffic switches back to the primary Ethernet controller.

The switch back to the primary Ethernet controller can be automatic or manually controlled, depending on the setup and operating system.

Note that only one controller in the redundant pair is active at any given time. For example, if the primary Ethernet controller is active, then the secondary Ethernet controller cannot be used for any other network operation.

Note: Your operating system determines the maximum number of IBM Netfinity 10/100 Fault Tolerant Adapters that you can install in the server. See the documentation that comes with the adapter for more information.

Considerations when combining failover and hotplug functions:

If your operating system supports hotplug PCI adapters and the optional redundant NIC adapter is installed in a hot-plug PCI slot, you can replace the NIC adapter without powering off the server — even if it is the primary Ethernet controller. Disconnecting the Ethernet cable from the primary Ethernet controller will cause the Ethernet traffic to switch automatically to the secondary Ethernet controller. This can be very useful if a faulty adapter causes a network problem, or if you want to upgrade the primary adapter hardware.

Note: If you hot-replace the primary adapter while the

Ethernet traffic is being handled by the secondary

Ethernet controller, the traffic does not automatically switch back to the primary adapter when the primary

adapter comes back online. See “Configuring for failover”.

Configuring for failover:

The failover feature currently is supported by Windows NT Server and IntraNetWare. The setup required for each operating system follows.

Windows NT Server:

IBM offers hot-plug support for Windows NT Server Version

4.0. Failover can work in conjunction with hot-plug support or independently. If you are not using hot-plug support, go to

“Windows NT Server failover setup” on page 103.

Windows NT Server hot-plug setup:

IBM Netfinity Hot Plug PCI for Windows NT Server 4.0 package is available for download from the IBM Web site at: http://www.pc.ibm.com/support

Enter the brand type of Server, click on Downloadable files and look for Hot Plug. The IBM Netfinity Hot Plug PCI for

Windows NT Server 4.0 package uses the Intel Desktop

Management Interface (DMI) to control hot-plug support for the Ethernet controllers. The Ethernet controller in your computer is DMI compliant. Download and install the following software in the order listed:

1. IBM Netfinity PCI Hotplug for Windows NT 4.0 Failover

DMI Agent

2. IBM Netfinity PCI Hotplug for Windows NT 4.0 Solution

102


3. IBM Netfinity 10/100 Fault Tolerant Adapter device drivers

Note: The order of installation is important. You must install the IBM Netfinity Hot Plug for Windows NT Server 4.0 package before you install the IBM Netfinity 10/100

Fault Tolerant Adapter driver. If you install the adapter device driver before the PCI Hot Plug Solution package, the adapter device driver will not recognize the hot-plug code. This happens because the adapter device driver only checks the NT registry for the Hot Plug package during installation. If the PCI

Hot Plug Solution package is added after the adapter device driver is installed, the adapter must be removed and added again in order for it to detect the

PCI Hot-Plug Solution code.

To install the IBM Netfinity PCI Hotplug for Windows NT 4.0

Failover DMI Agent:

1. Download the IBM Netfinity PCI Hotplug for Windows

NT 4.0 Failover DMI Agent file from the Netfinity Support web page and extract the files onto a diskette.

2. Insert the diskette into the diskette drive.

3. From the Start menu, select the Run option.

4. Type A:\SETUP.EXE in the Open box.

5. Click Ok. The setup wizard opens.

6. Follow the instructions that are given by the setup wizard until the program is installed.

7. Restart the server.

To install the IBM Netfinity PCI Hotplug for Windows NT 4.0

Solution package:

1. Download the IBM Netfinity PCI Hotplug for Windows

NT 4.0 Solution file from the Netfinity Support web page and extract the files onto a diskette.

2. Log on to Windows NT Server as a user in the Administrator group.

3. Insert the diskette into the diskette drive.

4. From the Start menu, select the Run option.

5. Type A:\SETUP.EXE in the Open box.

6. Click OK. The Setup wizard opens.

7. Follow the instructions given by the setup wizard until the program is installed.

Windows NT Server failover setup:

To install the IBM Netfinity 10/100 Fault Tolerant Adapter device drivers:

1. Add the redundant NIC adapter according to the instructions that are provided with the adapter.

2. Use the ServerGuide CDs to install the AMD PCNet

Ethernet Family adapter device driver.

3. Do not select the Grouping box at this point; you must first restart the machine.

4. From the Windows NT Server desktop, select Control

Panel, then select the Network icon, then select the

Adapters tab.

Installing options

103

5. Highlight one of the adapters that will be in the redundant pair and then click the Properties... button.

6. Check the Grouping box. This will show the possible combinations for redundant pairs.

7. Select the adapter pair you want and then select OK.

Note that the integrated Ethernet controller is located at

PCI C.

Two options are available for recovering from a failover condition. The options are determined by the Enable for DMI / Hot Swap Support checkbox. If the IBM Netfinity Hot Plug PCI for Windows NT Server 4.0 package is installed, this checkbox will appear at the bottom of the Adapter Properties panel. If you do not have the

IBM Netfinity Hot Plug PCI for Windows NT Server 4.0 package installed on the server, you will not see the

Enable for DMI / Hot Swap Support checkbox.

If the Enable for DMI / Hot Swap Support checkbox is not checked or is not present, traffic will automatically switch back to the primary adapter when the primary link status is restored. In this mode, the adapter cannot be hot-swapped. Users with the IBM Netfinity Hot Plug

PCI for Windows NT Server 4.0 package installed should check the Enable for DMI / Hot Swap Support checkbox.

If the Enable for DMI / Hot Swap Support checkbox is checked, traffic will remain on the secondary adapter until the user directs it to return to the primary adapter.

This can be done after the hot-swap replacement of the primary adapter or by using the DMI interface.

8. Select Close to exit from the Network setup.

When you restart the server, the failover function will be in effect.

If a failover occurs, a message is written to the NT Event

Viewer log. In addition, if the Enable for DMI / Hot Swap

Support checkbox is checked, a DMI alert will also be generated.

IntraNetWare:

The IBM PCI Hot Plug System Bus Driver Diskette for Novell

Netware V4.41, V4.42, and V5.0 is available for download from the IBM Web site at: http://www.pc.ibm.com/support

The failover function is now enabled. If a failover occurs:

• The operating system console generates a message.

• The custom counters for the device driver contain variables that define the state of the failover function and the location of the redundant pair. You can use the

NetWare Monitor to view the custom counters.

Note: If the primary adapter was hot-replaced while the

Ethernet traffic was being handled by the secondary

Ethernet controller, the traffic does not automatically switch back to the primary adapter when the primary adapter comes back online. In this case, issue the command:

104


LOAD

d

:\

path

\PCNTNW SCAN

where

d

and

path

are the drive and path where the driver is located. This command causes the device driver to locate the primary adapter and switch the

Ethernet traffic to it.

Ethernet port connector

The following table shows the pin-number assignments for the RJ-45 connector. These assignments apply to both

10BASE-T and 100BASE-TX devices.

2

3

4

Pin

1

Signal

Transmit data+

Transmit data-

Receive data+

Not connected

6

7

8

Pin

5

Signal

Not connected

Receive data -

Not connected

Not connected

Table 21. Ethernet RJ-45 connector pin-number assignments.

Advanced System Management ports

The server has three communication ports dedicated to the

Netfinity Advanced System Management processor. One port uses a standard D-shell serial-port connector, connector

C. The other two ports, which are used for the ASM Interconnect function, use a dual RJ-45 connector.

You can attach a dedicated modem to the D-shell systemmanagement connector on the rear of the server to communicate with the integrated Netfinity Advanced System Management processor.

The ASM Interconnect function uses the RJ-45 system-management connectors. This function enables you to connect the Advanced System Management processors of several rack-mounted servers so that they can communicate with each other in half-duplex mode.

The following illustration shows the connectors and lights for the Netfinity Advanced System Management Interconnect board.


Installing options

105

Þ

1Ý

Serial port

Þ

2Ý

Advanced System Management interconnect connectors

Þ

3Ý

Power LED

Þ

4Ý


Þ

5Ý

Service processor error

106


Cabling the server

The following illustration shows the cabling for a typical server configuration.

Notes:


2. Refer to the documentation that comes with your options for additional cabling instructions. It might be easier for you to route any cables before you install certain options.

3. Cable identifiers are printed on the cables that come with the server and options. Use these identifiers to connect the cables to the correct connectors. For example, the hard disk drive cables are labeled HDD.

Installing options

107

108


Netfinity Manager

Netfinity Manager provides powerful hardware systemsmanagement capabilities, including access to all systems on the network that are running Netfinity Manager or Client Services for Netfinity Manager. In addition to all standard Client

Services for Netfinity Manager functions, Netfinity Manager also features directory transfers and file, remote screen captures, and remote command-line sessions. Netfinity Manager also enables you to export data collected by System

Information Tool, System Profile, Software Inventory, and

System Monitor to a DB2, Lotus Notes, or SQL or DB2 via an open database connectivity (ODBC) database (ODBC export is available on Windows NT systems only). Finally,

Netfinity Manager enables some services to be started at scheduled times and dates for simplified, automated systems management.

Netfinity Manager also provides two powerful features that enable you to access the Netfinity Manager system and all

Netfinity Manager systems from a system that is not attached to the managing system network:

• Serial Connection Control

Use the Serial Connection Control service to use a Netfinity Manager system modem to establish a connection with any Netfinity Manager system that has a modem. Once this connection is established, the Netfinity Manager has full access to Netfinity Manager services, just as though the remote system were part of the managing system network.

• Netfinity Manager for Web

Netfinity Manager for Web enables access and remote control of the Netfinity Manager system over the Internet, using any system that has an Internet connection and a World Wide Web (WWW) browser. With the Netfinity Manager for Web, the Netfinity Manager systems can be accessed from anywhere in the world.

Managing your IBM Netfinity server with

Netfinity Manager

The copy of Netfinity Manager that is included with Server-

Guide entitles you to one Netfinity Manager installation. You are also entitled to additional installations of Client Services for Netfinity Manager. To use Netfinity Manager to monitor and manage this Netfinity server, install Netfinity Manager on a system in your network that you will use as a systemmanagement console, and then install Client Services for

Netfinity Manager on your Netfinity server. You can also install additional copies of Client Services for Netfinity Manager on other systems in your network. Furthermore, additional Netfinity Manager and Client Services for Netfinity

Manager licenses are available for purchase from your IBM representative.

Note: This section provides installation instructions for all operating systems supported by Netfinity Manager.

However, not all operating systems described in this

109

section are certified for use with all Netfinity server models. For a list of supported operating system for you Netfinity server model, see the Server Proven list at http://www.ibm.com.pc/compat

Netfinity Manager documentation

The Netfinity directory on the

ServerGuide Netfinity Applications

CD contains online versions (*.PDF format) of all Netfinity Manager documentation. For more information on

included documentation, see “Getting more information about Netfinity Manager” on page 139.

Netfinity Manager system requirements

The minimum system requirements for Netfinity Manager vary based on which supported operating system is running on your system.

• If you are installing Netfinity Manager for OS/2, see

“Netfinity Manager for OS/2 system requirements”.

• If you are installing Netfinity Manager for Windows 95

(or Windows 98), see “Netfinity Manager for Windows

95 and Windows 98 system requirements” on page

111.

• If you are installing Netfinity Manager for Windows NT,

see “Netfinity Manager for Windows NT system requirements” on page 112.

Netfinity Manager for OS/2 system requirements

The minimum system requirements for Netfinity Manager for

OS/2 are:

• OS/2 version 3.0 or later

• Approximately 19 MB–22 MB of hard disk space

(space required depends on system configuration)

• A LAN adapter card and one or more of the following communications protocols:

— IBM TCP/IP for OS/2 version 1.2 or later (required for Netfinity Manager with Web Enhancement)

— NetBIOS

Note: The Netfinity Manager NetBIOS requirements are three names, two sessions, and nine network control blocks (NCBs).

— IPX

— SNA (IBM Communications Manager/2 version

1.1 only)

Note: Systems using Netfinity Manager with

Microsoft SNA Server cannot communicate with systems that run the Microsoft SNA

Server client. Netfinity Manager supports only server-to-server communications between systems that run Microsoft SNA

110


Server software. However, Netfinity Manager systems running Microsoft SNA

Server can communicate with other Netfinity Manager systems using any of the other supported SNA stacks.

• A 9600 baud or greater modem (optional).

The hard disk requirement for Client Services for Netfinity

Manager is 6.5 MB–9 MB of hard disk space. All other system requirements are the same as for Netfinity Manager for

OS/2.

Note: Serial Connection Control will not function on systems that do not have a properly installed and configured modem.

Netfinity Manager for Windows 95 and

Windows 98 system requirements


Windows 95 are:

• Microsoft Windows 95 or later




— TCP/IP (must be WinSock Version 1.1-compatible; required for Netfinity Manager with Web

Enhancement)

— NetBIOS


— IPX

— SNA (PCOMM 4.1 or later SNA stack)

Note: Systems using Netfinity Manager with

Microsoft SNA Server cannot communicate with systems that run the Microsoft SNA

Server client. Netfinity Manager supports only server-to-server communications between systems that run Microsoft SNA

Server software. However, Netfinity Manager systems running Microsoft SNA

Server can communicate with other Netfinity Manager systems using any of the other supported SNA stacks.




Windows NT.

Note: Serial Connection Control will not function on systems that do not have a properly installed and configured modem.

Netfinity Manager

111

Netfinity Manager for Windows NT system requirements


Windows NT are:

• Microsoft Windows NT version 4.0 or later




— TCP/IP (must be WinSock Version 1.1-compatible; required for Netfinity Manager with Web

Enhancement)

— NetBIOS


— IPX

— SNA (Microsoft SNA Server version 2.11 with Service Pack 1 and WCPIC32.DLL dated 01/22/97 or later. This DLL is available from Microsoft)

Note: Systems using Netfinity Manager with Microsoft

SNA Server cannot communicate with systems that run the Microsoft SNA Server client. Netfinity Manager supports only server-to-server communications between systems that run Microsoft

SNA Server software. However, Netfinity Manager systems running Microsoft SNA Server can communicate with other Netfinity Manager systems using any of the other supported SNA stacks.




Windows NT.

Notes:

1. Serial Connection Control will not function on systems that do not have a properly installed and configured modem.

2. To most effectively manage Windows NT systems, any user that will be using Netfinity Manager on a Windows

NT system (locally or remotely) must have administrator-level access to the system.

Starting the Netfinity Manager installation program

For instructions on installing Client Services for Netfinity

Manager, see the documentation listed in “Getting more information about Netfinity Manager” on page 139.

To start the Netfinity Manager installation program on a system that is running Windows NT 4.0:

112


1. Start the computer with your operating system.

2. Place the

ServerGuide Netfinity Applications

CD into the CD-ROM drive.

3. Follow the instructions for your operating system below:

• OS/2 Warp Server a. From a command prompt, type

x: where

x

is the CD-ROM drive letter, and then press Enter. b. Type

SCOS2 and then press Enter. The ServerGuide Netfinity Applications windows opens.

c. Select IBM Netfinity Manager from the

Available Applications selection list.

Note: To install Client Services for Netfinity

Manager, select Client Services for

Netfinity Manager from the Available

Applications list and then refer to the

Client Services for Netfinity Manager

User’s Guide

for additional installation instructions.

d. Click Install Product to start the installation process.

• Windows 95, 98, or NT a. Click the Start button.

b. Click Run... from the Start button menu.

c. Type

x:\SCW95 where

x

is the drive letter of the CD-ROM drive in the Command Line field and then click OK. The ServerGuide Netfinity Applications windows opens.

d. Select IBM Netfinity Manager from the

Available Applications selection list.

Note: To install Client Services for Netfinity

Manager, select Client Services for

Netfinity Manager from the Available

Applications list and then refer to the

Client Services for Netfinity Manager

User’s Guide

for additional installation instructions.

e. Click Install Product to start the installation process.

4. Choose a drive and directory from which the Netfinity

Manager program files will be copied.

Type in the Directory to Install from field the drive and directory name where the Netfinity Manager program files are located. The default is the drive and directory from which the Netfinity Manager installation program was started.

5. Type in the Directory to Install to field the drive and directory in which to install the Netfinity Manager files.

Netfinity Manager

113

Enter the drive and directory name to which the Netfinity Manager program files will be copied. The default is

C:\NETFIN (on systems running OS/2) or C:\WNETFIN

(on systems running Windows 95 or Windows NT).

6. Click OK to save these settings and open the Netfinity

Manager Installation Program window.

7. Select installation options.

There is only one installation configuration for Netfinity

Manager. However, the Netfinity Manager program offers several installation options. Each option enables additional specialized feature of this product.

The available installation options are:

• Advanced System Management Support

Click Advanced System Management Support to install the Advanced System Management service on this system. Use this service to monitor and manage IBM Advanced System Management processors and adapters.

Important: If you install Advanced System Management support an enhanced version of the Serial Connection

Control service, named Dynamic

Connection Manager, will be installed instead of Serial Connection Control. For more information on Advanced System Management and the Dynamic Connection Manager service see the

Advanced System Management Information

section of this server library.

• Capacity Manager

Click Capacity Management to install the Capacity Management service on this system. Capacity

Management is a resource management and planning tool that is designed to enable network

114


managers and administrators to remotely monitor server performance.

• Remote Workstation Control

Click Remote Workstation Control to enable the

Remote Workstation Control service on this system. Use Remote Workstation Control to monitor or control the screen display of remote systems that are running Netfinity Manager or Client Services for Netfinity Manager.

• Update Connector Manager (NT 4.0, TCP/IP, and

Web Browser Required)

Click Update Connector Manager (NT 4.0,

TCP/IP, and Web Browser Required) if Netfinity

Manager is being installed on a system that will be used to manage system updates on client systems using updates that are available from the

IBM selection server.

• World Wide Web Enhancement (TCP/IP

Required)

Click World Wide Web Enhancement (TCP/IP

Required) if the Netfinity Manager is being installed on a system that will be used to manage other Netfinity Manager systems, and can be accessed and controlled remotely over the Internet using a World Wide Web browser.

8. Install Netfinity Manager.

Click Install to continue. The installation program copies all program files required by the installation configuration. A window appears, displaying the name of the file that is currently being copied.

Note: Click Cancel to stop the installation process.

Network communication drivers and the following Netfinity Manager services are installed:

• Alert Manager

• Alert on LAN® Configuration (available only on systems running Windows 95 or later or Windows

NT 4.0 or later)

• Capacity Management (available only on systems running Windows NT 4.0 or later)

• Cluster Manager (available only on systems running Windows NT 4.0 or later)

• Critical File Monitor

• DMI Browser (requires DMI Service Layer)

• ECC Memory Setup (requires ECC memory)

• Event Scheduler

• File Transfer

• Power On Error Detect

• Predictive Failure Analysis® (requires PFAenabled hard disk drive)

• Process Manager

• RAID Manager (requires RAID adapter)

• Remote Session

• Remote System Manager

• Remote Workstation Control

• Screen View

• Security Manager

Netfinity Manager

115

• Serial Connection Control

• Service Configuration Manager

• Service Processor Manager

• Service Manager

• Software Inventory

• System Diagnostics Manager

• System Information Tool

• System Monitor

• System Partition Access (requires System Partition)

• Update Connector Manager (available only on systems running Windows NT 4.0 or later)

• System Profile

• Web Manager Configuration (installed only if the

Netfinity Manager Installation with Web Enhancement installation configuration is selected)

Note: The graphical user interface (GUI) program files for DMI Browser, ECC Memory Setup, System

Partition Access, RAID Manager, and Predictive

Failure Analysis will be installed regardless of whether the system has a DMI Service Layer,

ECC Memory, a System Partition, a RAID adapter, or a PFA-enabled disk drive. This enables a network administrator to remotely access these services on other systems within a network. However, the installation program installs the base program that enables local use of the service only if the required hardware or system configuration is present.

9. Configure the Network Drivers.

If the installation configuration allows for network access, enter information regarding the communication protocols that are supported by the system. The Network Driver Configuration window will appear.

Follow these steps to continue configuring the system: a. Enter a System Name.

Enter a name for the system in the System Name field. This name will help other Netfinity Manager users identify the system on the network.

116


b. Select a Network Driver.

Select one of the available Network Drivers that are displayed in the Network Drivers field. Once selected, the Network Driver will assign a network address to the system.

Notes:

(1) The fields that appear beneath the Driver

Enabled check box will change depending on which Network Driver has been selected.

(2) When enabling the IPX or TCP/IP Network

Driver, the network address cannot be altered, and it will not appear on the screen.

No field will appear beneath the Driver

Enabled check box if the IPX or TCP/IP Network Driver is selected.

(3) When enabling the NetBIOS Network Driver, a network address will be selected and displayed in the Network Address field. To change this default name, enter any 1–8 character address. However, this address

must

be unique to the system. If this Net-

BIOS address is identical to the NetBIOS address of another system on the network, it will prevent Netfinity Manager from starting properly.

(4) When enabling the Serial Netfinity Manager driver, type a name that will be used to identify the system in the Unique Machine Dia-

lup Name field. This name can be up to 32 characters long, and must be unique to the system. If this name is not unique, it can prevent remote Netfinity Manager users from using the Serial Connection Control service to access the system.

c. Enable the Network Driver.

When all required information has been entered, click the Driver Enabled check box to activate the driver on startup.

If the system supports multiple network interfaces, add additional network drivers by repeating steps b and c.

d. Identify the system with System Keywords

(optional).

To make full use of the Remote System Manager’s discovery process, identify the system (and each of the Netfinity Manager systems that are on the network) with descriptive system keywords.

Enter these keywords in the appropriate System

Keywords fields.

e. Select Netfinity Manager Options (optional)

Click on the Options button to open the Netfinity

Manager Options window. The Netfinity Manager

Options window contains special options that affect Netfinity Manager network operations.

Available options include:

• Force Remote Logons

If the Force Remote Logons option is enabled, the system will not be able to save

Netfinity Manager

117

the User ID/Password combinations that were used when accessing remote systems.

This will force you to manually log on each time a remote stem is accessed.Service Execution Alerts

• Service Execution Alerts

If the Service Execution Alerts option is enabled, the Netfinity Manager Service Manager will generate a Netfinity Manager alert whenever one of

the user’s

Netfinity Manager services is started by a remote user.

The alert includes the name of the service that was run and information about the user that started the service.

• Show Network Support

If the Show Network Support option is enabled, the Netfinity Manager Support Program (or Network Interface) will be visible as a minimized process in the Windows NT 4.0 task bar. This enables the user to shut down the Netfinity Manager Support Program. If the Netfinity Manager Support Program is to remain invisible to the user, do not enable this option.

• Remote User Authorization for Screen

Access

If the Remote User Authorization for

Screen Access option is enabled, a remote user cannot use either Remote Workstation

Control or Screen View on your system without your permission. When this option is enabled and a remote user attempts to use one of these services on your system, a window will pop up on your desktop alerting you that a remote user is attempting to use the

Remote Workstation Control or Screen View service and asking whether you want to permit this user to use this service on your system. You can click Yes or No. If you do not make a selection within 15 seconds (for example, if you are not sitting at your system when the access attempt is made), Netfinity

Manager will automatically prevent the remote user from using the service on your system.

• Disable DNS Name Resolution

If the Disable DNS Name Resolution option is enabled, Netfinity Manager will use only a numeric TCP/IP address (for example,

8.24.67.32) to communicate with remote systems and will not attempt to resolve the numeric address into an alphanumeric,

Domain Name Server (DNS) address (for example, your.system.ibm.com). Select this option if you are using Netfinity Manager is a

WINS networking environment or if you are

118


using TCP/IP in an environment that does not have a Domain Name Server.

To enable one or more of the available Netfinity

Manager Options:

(1) Click Options....

(2) Select one or more Netfinity Manager options.

(3) Click Save.

f. Set the Network Time-out Value (optional).

The Network Time-out field shows the number of seconds that Netfinity Manager will attempt to communicate with a remote system that is not responding. If Netfinity Manager does not establish contact with the remote system within this time, it cancels the communication attempt. The

Network Time-out default setting is 15 seconds.

This default setting might not need to be altered.

g. Save the configuration and continue.

Click Save to save the configuration. Then, click

Exit to continue.

Note: The configuration can be changed later by double-clicking the Network Driver Con-

figuration object in the Netfinity Manager folder.

10. After finishing configuring the system for network access, the installation program displays a list of changes that must be made to the system configuration files, and asks whether the installation program should make the changes. For example, if Netfinity Manager for Windows 95 is being installed, the installation program will display a list of changes that must be made to the CONFIG.SYS file.

Click either Yes or No.

Note: These changes must be made to the system configuration for Netfinity Manager to run correctly.

• If you click Yes the installation program automatically makes the necessary changes to the system configuration.

• If you click No the commands are saved to a file named CONFIG.NEW in the destination directory

(and to AUTOEXEC.NEW, if appropriate) so that they can be added later.

11. The installation is now complete. Shut down and restart the system for the system configuration changes to take effect.

Netfinity Manager database support

Netfinity Manager supports the collection and export of a vast amount of system-specific data to a Netfinity Manager database.

Netfinity Manager databases can be created on database management systems using DB2®, Lotus Notes®, or

Microsoft SQL. Microsoft SQL is supported through open

Netfinity Manager

119

database connectivity (ODBC), and is available on systems running Netfinity Manager for OS/2, Windows 95, or Windows NT. If the system supports ODBC, the user can access and export DB2 data through ODBC as well. Once support for one or more of these databases has been installed along with Netfinity Manager, data can be exported from these

Netfinity Manager services:

• Alert Manager

• Software Inventory

• System Information Tool

• System Profile

• System Monitor

Information on how to install and configure support for database export follows.

• If support for DB2 database export is being installed,

see “DB2 database support”.

• If support for Lotus Notes database export is being

installed, see “Lotus Notes database support” on page

124.

• If support for ODBC database export is being installed,

see “ODBC database support” on page 126.

DB2 database support

Support for DB2 database export is automatically configured during installation of the Netfinity Manager. However, the database system itself must be configured. Instructions for configuring the database follow.

A raw data dump to a file is also available and will run without a database.

System requirements

Netfinity Manager DB2 database export is supported on systems running Netfinity Manager for OS/2, Netfinity Manager for Windows 95, Netfinity Manager for Windows 98, and Netfinity Manager for Windows NT. For more informa-

tion about supported version numbers refer to Table 22 on

page 129 and Table 23 on page 131.

Attention:

Using Netfinity Manager database support with systems running unsupported versions of DB2 or the DB2 Client might cause unpredictable results and might halt the system.

See the

DB2 Installation Guide

for general requirements and supported protocols.

Installing and configuring the database

The following information describes the steps to install and configure the DB2 database.

Note: If your primary system is OS/2, refer to “Installing the database on OS/2” on page 121.

1. Start a DB2 command window.

Note: If it is not already running, start the DB2 database manager.

2. Type the following command:

120


DB2 CREATE

databasename

ON

d

where

•

•

databasename d

is the name of the database

is the drive where the database is created

3. Press Enter.

4. Next, you must configure the tables for ODBC database support. For information on configuring the data-

base for ODBC, refer to “ODBC database configuration” on page 127. For information on creating the tables, refer to “Creating the Netfinity Manager tables” on page 127.

5. Finally, you must bind the database. For information on

binding the database, refer to “Activating the database”.

Installing the database on OS/2:

1. Insert the Netfinity Manager CD into the CD-ROM drive

(in this example, drive D; individual drive letters might be different).

2. Start an OS/2 window or full-screen session.

3. Make the CD-ROM drive the active drive.

Type D: and then press Enter.

4. Type the following command at the OS/2 prompt:

NETFINDB CREATE /DBNAME=

databasename

/DRIVE=

d

where

databasename

is the name of the database and

d

is the drive where the database will be located.

Note: If any part of the database already exists, the utility program will create only the portions of the database that are missing.

5. Press Enter.

Activating the database

The following information describes how to connect, bind, and grant privileges to the database.

1. Connecting to the Database a. Start a DB2 command window.

b. Type the following command:

DB2 CONNECT TO

databasename

where

databasename

is the name of the database as specified in the database installation step.

c. Press Enter.

2. Bind the package and the database

To prepare SQL statements stored in the bind file and store the package in the database, perform the following steps from a system on which Netfinity Manager for

OS/2, Netfinity Manager for Windows 95, or Netfinity

Manager for Windows NT has been installed: a. Open a DB2 command window.

b. In the DB2 command window, type the following command:

DB2 BIND x:

\ directory

\DB2SQLC0.bnd

where x: \ directory is the name of the drive and directory where Netfinity Manager is installed.

c. Press Enter.

Netfinity Manager

121

Granting and revoking database privileges

The following information describes how to grant and revoke database privileges.

Note: If your primary system is OS/2, refer to “Database privileges on OS/2 systems”.


Notes:

a. If it is not already running, start the DB2 database manager.

b. If you are not connected to the DB2 Netfinity database connect to the database now.

2. Type the following command:

DB2 GRANT

privilegecode

ON TABLE

tablename

TO

userid

where

•

privilegecode

is one of the following privilege codes:

— ALL

— ALL PRIVILEGES

•

Note: Grants all the appropriate privileges, except CONTROL, on the database.

— ALTER

— CONTROL

— DELETE

— INDEX

— INSERT

— REFERENCES

— SELECT

— UPDATE

tablename

is the name of the table as specified during database installation. A listing of the Netfinity database table names can be found in the

Netfinity User’s Guide

(Appendix H: Netfinity Relational Database Tables).

•

Note: The Netfinity Database Administration Tool can also be used to GRANT or REVOKE

userid

privileges.

is the user ID to be granted access

3. Press Enter to execute the command.

To revoke privileges, substitute REVOKE for GRANT in the command line.

Database privileges on OS/2 systems:

1. Use the GRANT EXECUTE command to enable Netfinity Manager to access the database.

Type the following command at the OS/2 prompt:

DB2 GRANT EXECUTE ON PACKAGE NETFIN.DB2SQLC0 TO

PUBLIC and then press Enter.

Note: Specify PUBLIC or authorize only specific manager systems. To limit access to the database, substitute the authorization name of the managing system for PUBLIC.

2. Use the CONNECT RESET command to disconnect current users from the database.

Type the following command at the OS/2 prompt:

122


DB2 CONNECT RESET and then press Enter.

3. Use the NETFINDB GRANT command to grant (or revoke) database privileges.

To grant or revoke table privileges on OS/2: a. Insert the Netfinity Manager CD into the CD-ROM drive (in this example, drive D; individual drive letters might be different).

b. Make the CD-ROM drive the active drive.

Type D: and then press Enter.

c. Type the following command:

NETFINDB GRANT /ID=

id

PUBLIC

/DBNAME=

databasename

/PRIV=

privilegecode

where

•

•

•

id

is the user ID to be granted access

databasename

is the name of the database as specified during NETFINDB execution

privilegecode

is one of the following privilege codes:

— ALL

— ALTER

— CONTROL

— DELETE

— INDEX

— INSERT

— REFERENCES

— SELECT

— UPDATE d. Press Enter to execute the command.

Note: Use PUBLIC or authorize only a specific ID or group name. Netfinity Manager update programs use the DB2SQLC0 package and do not require specific table privileges.

To revoke privileges, substitute REVOKE for GRANT in the command line.

To configure Netfinity Manager to discontinue export

data through ODBC for use on DB2, refer to “ODBC database support” on page 126.

Cataloging the database in the managing system:

If the manager is using a remote database, catalog the node the database resides on and then catalog the database to that node.

Once this step has been completed, the name of the Netfinity Manager database will appear in the System Information

Tools Database Selection window.

Deleting the database

The following information describes how to delete the database for all supported operating systems.

Note: If your operating system is OS/2, refer to “Deleting the database on OS/2” on page 124.


2. Type

DB2 DROP DATABASE

databasename

Netfinity Manager

123

where

databasename

is the name of the database as specified during the database installation.

3. Press Enter.

Deleting the database on OS/2:

1.Insert the

Netfinity

Manager CD-ROM

into the database server CD-ROM drive (in this example, the CD-ROM drive is E).

2. Start an OS/2 window or full-screen session.

3. Make the CD-ROM drive the active drive.

Type E: and press Enter.

4. Type the following command at the OS/2 prompt:

NETFINDB DELETE /DBNAME=

databasename

where

databasename

is the name of the database as specified during NETFINDB execution.

5. Press Enter.

To configure Netfinity Manager to discontinue export data

through ODBC for use on DB2, refer to “ODBC database support” on page 126.

Lotus Notes database support

To enable the Netfinity Manager to export system data to a

Lotus Notes database, the following must be done:

1. Install the Netfinity Manager database template on the

Lotus Notes server.

2. Enable Netfinity Manager to export to the Lotus Notes server.

Instructions on installing the Lotus Notes database template and enabling the Netfinity Manager to export to the Lotus

Notes database follow.


The minimum requirements for Netfinity Manager to export data to a Lotus Notes database are:

• Lotus Notes

• Lotus Notes client

For information on what versions of Lotus Notes and the

Lotus Notes client are supported, see Table 22 on page 129.

See the

Notes Administrator’s Guide

for general system requirements and supported communications protocols.

Installing the database

To enable Netfinity Manager to export system data to a

Lotus Notes database, install the Netfinity Manager database template on the Lotus Notes server. During Netfinity

Manager installation, a Lotus Notes database template file

(named NETFINDB.NTF) was copied to the Netfinity Manager program directory. To install the database template on the Lotus Notes server:

1. Copy NETFINDB.NTF from the Netfinity program directory to the Notes data directory on the Lotus Notes server.

2. Start Lotus Notes on the server.

124


3. Click New Database... from the Notes File pull-down menu.

This opens the New Database window.

4. Click Netfinity Database from the Template selection list.

5. Check the Inherit Future Design Changes check box.

This enables future releases of Netfinity Manager to automatically apply changes to this Netfinity Manager database.

6. Click Local from the Servers selection list.

Note: When installing the database on a remote server, select the name of the remote server from the Servers list.

7. Type in the Filename field:

NETFINDB.NSF

8. Type in the Title field:

Netfinity Database

9. Click New to create the database and close the New

Database window.

10. Double-click the Netfinity Database icon in the Lotus

Notes workspace.

11. Click Database in the File pull-down menu.

12. Click Access Control... in the Database pull-down menu.

13. Set the Access Level for all Netfinity Manager systems that will be exporting data to this database to Editor.

14. Check the Can Delete Documents check box.

15. Click OK.

Once the Lotus Notes database is installed, enable Netfinity

Manager systems to export to the Lotus Notes server.

• If the Netfinity Manager system is running Netfinity

Manager for OS/2, ensure that the Lotus Notes directories are included in the CONFIG.SYS file LIBPATH,

PATH, and DPATH statements. If the directories are not included in these statements, it is not possible to export to the Lotus Notes database.

• If the system is running Netfinity Manager for Windows

NT, ensure that the Lotus Notes directory path is included in the Global Windows NT environment settings.

• If the system is running Netfinity Manager for Windows

95, ensure that the Lotus Notes directories are included in the AUTOEXEC.BAT file PATH statement. If the directories are not included in this statement, it is not possible to export to the Lotus Notes database.

Once these steps have been completed, export system information from Netfinity Manager to an easy-to-browse

Lotus Notes database.

Browsing the Netfinity Manager Lotus Notes database

To browse the data contained in the Netfinity Manager Lotus

Notes database:

Netfinity Manager

125

1. Open the Netfinity Database object in the Lotus Notes

Workspace.

2. Select from the View pull-down menu the section of the

Netfinity Manager database to be browsed.

The Netfinity Manager database is divided into sections that contain data gathered by specific Netfinity Manager services. Click the name of the service that gathers the data to be viewed (for example, Alert Logs).

Note: Some menu selections will contain submenus.

3. Information contained in the part of the Netfinity Manager database that has been selected is now listed in the window. For more detailed information about any displayed data item, double-click the data item.

4. Some data items can be expanded to reveal additional information. These items are identified by a plus sign

(+) in the left side border of the Notes window, beside the name of the data item. To expand the data item, select the item and then click Expand in the View pulldown menu.

ODBC database support

Netfinity Manager supports exporting data via ODBC for use on SQL or DB2 database systems.

Note: ODBC database export is available only on systems that are running Netfinity Manager.


The minimum requirements for Netfinity Manager ODBC database export are:

• Windows NT

— ODBC

— ODBC support for one or more of the following database management systems (DBMS):

– IBM DB2

– Microsoft SQL Server

• Windows 95, with:

— ODBC

— ODBC support for one or more of the following database management systems:

– IBM DB2

– Microsoft SQL Server

• OS/2

— Microsoft SQL Server (using the Visigenic driver provided with Microsoft SQL Server)

or

— IBM DB2

For detailed information about supported ODBC plat-

forms, see Table 22 on page 129 and Table 23 on page

131.

Note: The ODBC database name must not be longer than 8 characters.

126


ODBC database configuration

This section describes the procedures you must complete before Netfinity Manager can create the Netfinity Database

Tables using ODBC.

1. Define the NETFIN ID so the Netfinity Database

Administration can create the Netfinity Database tables with a table qualifier of NETFIN.

Attention:

NETFIN is a restricted user ID. The password is not retained by Netfinity

Database Administration after use. Do not use this ID for exports.

Notes:

a. In OS/2 and Windows 95, NETFIN must either be the owner of the database or must be given administrator authority.

b. In Windows NT, when exporting to DB2, NETFIN must either be the owner of the database or be defined as a system administrator through the NT

User Manager for Domains or the NT User Manager.

In Windows NT, when exporting to MS SQL, NET-

FIN must be the owner of the database or be given table create rights.

2. Create the database with the appropriate relationship with the NETFIN ID.

3. Make a database ODBC source either using the ODBC tools shipped with the operating system or the database.

4. On Windows NT, configure the Netfinity Support Program to export data using the ODBC database. a. Open Services from the Control Panel.

b. Click Netfinity Support Program from the Ser-

vices field, then click Startup.

c. Click Automatic in the Startup Type button group.

d. Click This Account in the Log On As field group.

Enter in the This Account field the user name of the account that made this database an ODBC source.

e. Click OK.

Note: If the Event Scheduler or Alert Manager will be used to export data using ODBC, continue to have the ID which made the database an ODBC source logged on during the time Event Scheduler will be exporting data.

Creating the Netfinity Manager tables

To create the tables needed to enable Netfinity Manager to export data:

1. Open the Netfinity Manager Database Administration service.

The Netfinity Manager Database Administration service is found in the Netfinity Manager folder or Netfinity

Manager program group. Double-click this icon to open the Netfinity Manager Database Administration window.

Netfinity Manager

127

2. Select a DBMS.

Click in the Select DBMS listing the name of the DBMS which Netfinity Manager will be using to export data.

3. To create the Netfinity Manager table groups within the database, click Create and then click OK to open the

Database Server window.

The following table actions are also available:

• Delete

To remove the Netfinity Manager table groups from the database, click Delete and then click OK to open the Database Server window.

• Grant

Permits access to a database for a specified user

ID. To grant access: a. Click Grant.

b. In the User ID field type the user ID that will be permitted to access the database.

c. Select privileges for this ID.

128


All privileges (Insert, Delete, Select, and

Update) are selected by default. A user ID must have all of these privileges to export data to the database.

d. Click OK to open the Database Server window.

• Revoke

Disables access to a database for a specified user

ID. To revoke access: a. Click Revoke.

b. In the User ID field type the user ID that will have access to the database revoked.

c. Deselect privileges to be revoked for this ID.

All privileges (Insert, Delete, Select, and

Update) are selected by default. A user ID must have all of these privileges to export data to the database. Some or all of these privileges can be revoked.

d. Click OK to open the Database Server window.

4. Select the database within which the table groups will be created.

5. Click OK.

The Netfinity Manager Database Access window opens.

6. Type in the User ID field netfin netfin

is the qualifier name of the Netfinity Manager database.

7. In the Password field type the password that enables access to the Netfinity Manager database.

8. Click OK.

As the information is processed, a

Creating tables

status message should be displayed. When the operation completes, a

Requested Action Completed

message should be displayed.

Supported and certified databases

The following tables show databases and operating systems that are certified for use with this release of Netfinity Manager.

Table 22. Supported Netfinity Databases for Windows.

Reference by operating system and database client version.

Product

IBM DB2

Version 2.1.2

Windows

95

Yes

Windows

NT 3.51

Yes

Windows

NT 4.0

Yes

Netfinity Manager

129



Product Windows

95

Yes

Windows

NT 3.51

Yes

Windows

NT 4.0

Yes IBM DB2

Universal

Database 5.0

ODBC - IBM

DB2 Version

2.1.2

ODBC - IBM

DB2

Universal

Database 5.0

ODBC -

Microsoft

SQL Version

7.0

ODBC -

Microsoft

SQL Version

6.5

Lotus Notes

Version 4.5.2

Lotus Notes

Version

4.5.3a

Lotus Notes

Version 4.6

Lotus Notes

Version 4.6a

Lotus Notes

Version 4.63

Oracle

Version 7.3

Yes, DB2

Driver

Yes, DB2

Driver

Yes,

Microsoft

SQL Driver

Yes,

Microsoft

SQL Driver

Yes

Yes

Yes

Yes

Yes

Yes, DB2

Driver

Yes, DB2

Driver

Yes,

Microsoft

SQL Driver

Yes,

Microsoft

SQL Driver

Yes

Yes

No

No

No

Yes, DB2

Driver

Yes, DB2

Driver

Yes,

Microsoft

SQL Driver

Yes,

Microsoft

SQL Driver

Yes

Yes

Yes

Yes

Yes

Oracle

Version 8.0

Sybase SQL

Version 11.0

Yes, Oracle

Driver

Version

2.0.3.1.1

Yes, Oracle

Driver

Version

2.0.3.1.1

Yes, Oracle

Driver

Version

2.0.3.1.1

Yes, Oracle

Driver

Version

8.0.3.0.0

Yes, Sybase

Driver

Version

10.0.3T4

No

Yes,

Sybase

Driver

Version

10.0.3T4

Yes, Oracle

Driver

Version

8.0.3.0.0

Yes, Sybase

Driver

Version

10.0.3T4

130




Product Windows

95

Windows

NT 3.51

Windows

NT 4.0

Note: The above applies to Netfinity Manager Release

5.2.0 and later.

Table 23. Supported Netfinity Databases for OS/2.


Product

IBM DB2 Version 2.1.2

IBM DB2 Universal

Database 5.0

ODBC - IBM DB2

Version 2.1.2

OS/2 Warp

Connect

Yes

Yes

Yes, DB2

Driver

OS/2 Warp

Yes

Yes

4.0

Yes, DB2

Driver

ODBC - IBM DB2

Universal Database 5.0

ODBC - Microsoft SQL

Version 7.0

ODBC - Microsoft SQL

Version 6.5

Lotus Notes Version

4.5.2

Lotus Notes Version

4.5.3a

Yes

Yes

Lotus Notes Version 4.6

No

No Lotus Notes Version

4.6a

Lotus Notes Version

4.63

Oracle Version 7.3

Yes, DB2

Driver

Yes, DB2

Driver

Yes, Visigenic

Driver Version

1.10

No

No No

No

No

Yes

Yes

No

No

No

No

Oracle Version 8.0

Sybase SQL Version

11.0

No

No

No

No

Note: The above applies to Netfinity Manager Release

5.2.0 and later.

Netfinity Manager

131

Starting Netfinity Manager

To start Netfinity Manager:

1. Open the Netfinity Manager folder or program group.

During installation of Netfinity Manager, a Netfinity

Manager folder (OS/2, Windows 95, or Windows NT

4.0 only) or a Netfinity Manager program group (Windows NT 3.51 only) was added to the Desktop. The

Netfinity Manager folder or program group contains the

Netfinity Manager Service Manager object.

Notes:

a. In your Netfinity Manager folder or program group is a document titled

Read Me First

, which contains information about Netfinity Manager that might not be covered in your documentation.

b. The Netfinity Manager folder also contains the

Network Driver Configuration object, which you can use to reconfigure your network protocols and system keywords, and the Netfinity Manager

Database Tables object, which contains a handy online reference for all of the data tables in the

Netfinity Manager database. For more information

on Netfinity Manager database support see “Netfinity Manager database support” on page 119.

c. The Netfinity Manager folder also contains a Netfinity Database Administration object. You can use

Netfinity Database Administration to configure

Netfinity Manager database support. For more information on Database Administration, see

"ODBC Database Support" in

Netfinity Manager

Quick Beginnings

.

2. Start the Netfinity Service Manager.

To start the Netfinity Service Manager, double-click the

Netfinity Service Manager object.

Netfinity Manager Service Manager

All Netfinity Manager services that are supported by the operating system can be started from the Netfinity Manager

Service Manager window. The services that are available for use depend on the installation configuration that was selected during installation.

132


To start any Netfinity Manager service that appears in the

Service Manager window, double-click the icon for that service. To start a Netfinity Manager service on a remote system, use the Remote System Manager service.

Netfinity Manager service descriptions

Each Netfinity Manager service consists of a base program and a graphical user interface (GUI). The service base programs enable Netfinity Manager to remotely access the individual services, but do not allow for local access. The service GUIs, when functioning along with their respective base program, enable access to the service.

Some services are available only on systems with certain system configurations. These services are:

• Alert on LAN Configuration (available only on systems running Windows 95 or later or Windows NT 4.0 or later)

• Capacity Management (available only on systems running Windows NT 4.0 or later)

• Cluster Manager (available only on systems running

Windows NT 4.0 or later)

• DMI Browser (requires DMI Service Layer)

• ECC Memory Setup (requires ECC memory)

• Predictive Failure Analysis (requires a PFA-enabled hard disk drive)

• RAID Manager (requires a RAID hard disk drive subsystem)

• System Partition Access (requires a built-in System

Partition)

• Update Connector Manager (available only on systems running Windows NT 4.0 or later)

Brief descriptions of each of the Netfinity Manager services follow. Complete instructions on how to use each of these services can be found in the service-specific chapters of the

Netfinity Manager User’s Guide

.

Netfinity Manager

133

Advanced System Management

The Advanced System Management service provides extensive functionality available for your IBM PC Server

Advanced System Management Adapter, Netfinity

Advanced System Management PCI Adapter, or Netfinity

Advanced System Management Processor. With the

Advanced System Management service, you can configure system management events (such as POST, loader, and operating system time-outs or critical temperature, voltage, and tamper alerts). If any of these events occurs, the

Advanced System Management service can be configured to use a modem or your Netfinity Manager system to automatically forward a Netfinity alert to other Netfinity Manager systems or to a numeric or alphanumeric pager.

Alert Manager

The Alert Manager is an extendable facility that allows receiving and processing of application-generated alerts. A variety of actions can be taken in response to alerts, including logging alerts, notifying the user, forwarding the alert to another system, executing a program, playing a WAV file

(available only on multimedia systems), generating an

SNMP alert message, dialing out to a digital pager service

(available only on systems that have a modem), or taking an application-defined action. Actions are user-definable, using a flexible action management interface.

Also, an extensive, detailed log is kept of all alerts received by the Alert Manager. Logged information includes date and time the alert was received, type and severity of the alert, the ID of the application that generated the alert, as well as any text that was generated and any action taken by the

Alert Manager. Individual or multiple alerts can be selected from the log and printed for later reference, or deleted once problems are corrected. This service is available for standalone use and network use.

Alert on LAN configuration

Use the Alert on LAN configuration service to configure monitoring options of Alert on LAN-capable systems locally and remotely. Systems with Alert on LAN capability provide critical status information about system states. The data is reported by hardware or software (depending upon whether the systems in currently powered on or not) using TCP/IP.

Capacity Management

Capacity Management is an easy-to-use resource management and planning tool for network managers and administrators, allowing you to remotely monitor the performance of servers on the network.

Cluster Manager

Cluster Manager is an application designed to enhance the cluster management capabilities of the Microsoft Cluster

Server (MSCS) administration console, included with

Microsoft Windows NT Version 4.0 Enterprise Edition. Cluster Manager builds on the power of MSCS, providing an integrated graphical interface that enables you to quickly and easily monitor and manage the clustered systems on your network. This service is available only on systems running

Windows NT Workstation 4.0.

134


Critical File Monitor

Critical File Monitor can warn you whenever critical system files on the system are deleted or altered. Critical File Monitor makes it simple to generate Netfinity alerts when an important System File (such as the CONFIG.SYS file) changes date, time, size, or when it is deleted or created.

Critical File Monitor can also be used to monitor any other files that reside on a Netfinity Manager system.

DMI Browser

DMI Browser enables you to examine information about the

DMI-compliant hardware and software products installed in or attached to the system.

ECC Memory Setup

The ECC Memory Setup allows for monitoring of ECC memory single-bit errors, and can automatically "scrub," or correct, the ECC memory when errors are detected. Also, a running count of single-bit errors can be kept, and can set a single-bit error threshold that will cause a nonmaskable interrupt (NMI) if the ECC single-bit error threshold is exceeded. This service is available for both stand-alone and network use by any system that has ECC memory.

Event Scheduler

Use Event Scheduler to automate many Netfinity Manager services. With Event Scheduler, you can automatically gather and export System Information Tool, System Profile, and Software Inventory data, distribute or delete files, restart systems, execute commands, and access and manage System Partitions on all of the Netfinity Manager systems on the network. Scheduled events can be performed one time only, or can be performed according to a user-defined schedule.

File Transfer

Use the File Transfer service to easily send, receive, or delete files or entire directories to and from remote Netfinity

Manager systems on the network.

Power-On Error Detect

The Power-On Error Detect service can warn you immediately when a remote Netfinity Manager system has start-up problems, enabling you to react quickly to problems and minimize downtime.

Predictive Failure Analysis

The Predictive Failure Analysis (PFA) service enables continual monitoring and managing of PFA-enabled hard disk drives. A PFA-enabled hard disk drive features hardware designed to help detect drive problems and predict drive failures before they occur, thus enabling you to avoid data loss and system downtime.

Process Manager

Use Process Manager to view detailed information about all processes that are currently active on any system. It is also possible to stop or start processes and generate Netfinity

Manager alerts if a process starts, stops, or fails to start within a specified amount of time after system startup.

RAID Manager

The RAID Manager service can monitor, manage, and configure an assortment of Redundant Arrays of Independent

Netfinity Manager

135

Disk (RAID) adapters and arrays without requiring the RAID system to be taken offline to perform maintenance. Use the

RAID Manager to gather data about the system RAID array and RAID adapter, rebuild failing drives, add (or remove) logical drives, perform data integrity tests, and many other

RAID system tasks. This service is available for stand-alone use and network use by any system that has a supported

RAID adapter.

Remote Session

Use Remote Session to establish a fully active command session with any remote Netfinity Manager system.

Remote System Manager

Use Remote System Manager to access and manage any

Netfinity Manager service on any Netfinity Manager system in the network. The Netfinity Manager system on the network is organized into easy-to-manage logical groups that can be updated automatically using the auto-discovery feature.

Remote Workstation Control

Remote Workstation Control can monitor or control the screen display of a remote system that is running Netfinity

Manager (or Client Services for Netfinity Manager). Once you initiate a Remote Workstation Control session with another Netfinity Manager system, you can passively monitor events that are occurring on the display of the remote system or actively control the remote system desktop. When you initiate an active Remote Workstation Control session, all clicks and keystrokes that are entered on your system are automatically passed to the remote system. With Remote

Workstation Control, you can remotely start programs, open and close windows, enter commands, and much more.

Screen View

The Screen View service takes a "snapshot" of the system graphic display or any remote system running Netfinity Manager or Client Services for Netfinity Manager and displays it on the screen. These snapshots can be saved as bitmaps and viewed later.

Security Manager

The Security Manager service can prevent unauthorized access to some or all of the Netfinity Manager services. It uses incoming user ID and password combinations, and is available for network use only.

Serial Connection Control

The Serial Connection Control service enables remote systems running Netfinity Manager to access the system through a phone line and modem. With the Serial Connection Control service, you do not have to be attached to a network to benefit from the outstanding remote system access, monitoring, and management capabilities of Netfinity Manager.

Note: The system

must

have a properly installed and configured modem that supports at least 9600 baud for the Serial Connection Control service to function.

136


Service Configuration Manager

Service Configuration Manager can save the configuration of a Netfinity Manager service from a selected system to a service configuration file (SCF). Once created, SCF files can be used by Event Scheduler to restore the configuration to the same system, or it can be used (in conjunction with

Event Scheduler) to duplicate that configuration on other similar systems you choose.

Software Inventory

Software Inventory enables the user to create and manage software product dictionaries that can be used to easily maintain an inventory of all application programs installed on the system.

System Diagnostics Manager

System Diagnostics Manager enables you to initiate a variety of diagnostic tasks on systems that support ROM-based diagnostics. The results of all previously run diagnostic sessions are stored and can be examined using System Diagnostics Manager to help diagnose and resolve system problems.

System Information Tool

The System Information Tool enables quick and convenient access to detailed information on the hardware and software configurations of the system. System Information Tool gathers information about almost any computer; however, the most detail is provided when this service is used with IBM computers. This service is available for both stand-alone and network use.

System Monitor

The System Monitor provides a convenient method of charting and monitoring the activity of a number of components in a system, including processor usage, disk space used, and

ECC memory errors. These convenient monitors are detachable and scalable, enabling only the monitors needed to remain available at all times. Use the System Monitor

Threshold Manager to set threshold levels for any of the monitored components. When exceeded, these thresholds will generate user-configured alerts.

Data is continually collected from the time the system starts.

A sophisticated data-handling technique is used to weigh the individual values, average concurrent samples, and post single values that accurately reflect long-term system activity.

This technique allows system activity records to be maintained without creating enormous data files. This service is available for both stand-alone and network use.

System Partition Access

The System Partition Access allows for greatly simplified system partition file handling, both locally and remotely.

Individual files and entire directories can be renamed or deleted from the system partition. Individual files can be renamed, deleted, or copied into the system partition. Also, the entire partition can be backed-up, restored, or deleted.

This service is available for stand-alone use and network use by any system that has a System Partition.

Netfinity Manager

137

System Profile

The System Profile provides a convenient notebook of pertinent data about a particular user or system. It features many predefined fields for extensive user-specific data, including name, address, office number and location, and phone number. System Profile also includes many predefined fields for system-specific data that might not be available to the System Information Tool, including model and serial numbers and date of purchase. Finally, there are many user-definable miscellaneous fields that can be used to hold any data the user or administrator requires.

Update Connector Manager

Use Update Connector Manager to quickly and easily gather information about various updates that are available for your client systems. Once available updates are discovered, use

Update Connector Manager to apply updates to your systems remotely. Updates can be applied to individual systems, or you can apply multiple updates to multiple systems, all from Netfinity Manager. You can also use Update Connector Manager to remove previously applied updates.

Update Connector Manager also includes a scheduler that you can use to discover, apply, or remove updates automatically and periodically.

Web Manager Configuration

Use the Web Manager Configuration service to limit access to the Netfinity Manager for Web to user-specified TCP/IP host or ranges of TCP/IP host addresses. Enable or disable the Netfinity Manager for Web and specify the TCP/IP port number to which the Netfinity Manager Web server functions.

Delaying Netfinity Manager startup on

OS/2 systems

In some cases, it might be necessary for you to delay the automatic startup of the Netfinity Manager Network Interface

(NETFBASE.EXE) in order to allow other time-sensitive applications to start up correctly or to allow your system to fully configure itself prior to beginning network operations.

NETFBASE.EXE includes a parameter (WAIT) that you can use to specify the number of seconds that NETFBASE.EXE will wait before starting.

During Netfinity Manager installation, the Netfinity Manager

Network Interface object is placed in the Startup folder. To configure Netfinity Manager to wait a specified number of seconds before starting:

1. Shut down the Netfinity Manager Network Interface if it is running.

2. Open the Startup folder.

3. Using the right mouse button, click the Netfinity Man-

ager Network Interface object. This will open the Netfinity Manager Network Interface context menu.

4. Click Settings to open the Netfinity Manager Network

Interface Settings notebook.

5. In the Parameters field type

WAIT:

x

138


where

x

is the number of seconds that you want the

Netfinity Manager Network Interface to wait before starting.

6. Close the Netfinity Manager Network Interface Set-

tings notebook.

With the WAIT parameter set to

x

, whenever you start your system, the Netfinity Manager Network Interface will wait

x

seconds before starting.

Note: This feature is available only on systems that are running OS/2.

Getting more information about Netfinity

Manager

Complete information on how to use Netfinity Manager (as well as Client Services for Netfinity Manager) is included in

Adobe Acrobat format on the Netfinity Manager CD.

The \DOCS subdirectory contains the following files:

Filename Document Title Description

DOCSREAD.ME

DOCSREAD.ME

Text file that contains brief descriptions of each of the

Adobe Acrobatreadable PDF file contained in this directory.

README.SCO

Client Services for Netfinity

Manager for SCO

UnixWare Read

Me

Text file that contains installation and setup information for Client

Services for

Netfinity Manager for SCO

UnixWare.

NFMGRQB.PDF

Netfinity Manager

Quick Beginnings

Installation and setup information for Netfinity

Manager.

NFMGRUG.PDF

Netfinity Manager

User’s Guide

Detailed information on how to use

Netfinity

Manager.

Netfinity Manager

139

Filename Document Title

NFMGRCR.PDF

Netfinity Manager

Command

Reference

Description

Detailed information on

Netfinity Manager command line functions.

NFCSVCQB.PDF


Manager Quick

Beginnings

NFSVCUG.PDF

NFSVCNW.PDF


Manager User’s

Guide


Manager for

NetWare User’s

Guide

Installation and setup information for Client

Services for

Netfinity

Manager.

Detailed information on how to use Client

Services for

Netfinity

Manager.

Installation, setup, and usage information for


Manager for

NetWare.

ASMUPDT.PDF

Advanced

System

Management

Information

Updated information on the Advanced

System

Management and

Dynamic

Connection

Manager services. These services are included with this version of

Netfinity

Manager.

NFSCOBAS.PDF


Manager for SCO

UnixWare User’s

Guide

Installation, setup, and usage information for


Manager for SCO

UnixWare.

140


Installation options

This appendix describes methods for performing automated installations of Netfinity Manager and creating customized

Netfinity Manager installations.

Automated installation

If the system has a CID-enabled (CID stands for customization, installation, and distribution) software distribution manager utility (such as LAN CID, included with IBM Network

Transport Services/2), Netfinity Manager can be installed on systems within the network by using the Netfinity Manager installation program command line parameters and response file. First, a source directory must be created for the installation.

To create a source directory for a Client Services for Netfinity

Manager installation:

1. Create a new directory on your system. This new directory will serve as a source directory for the program files.

2. Copy the files from the appropriate Client Services for

Netfinity Manager directory location on the CD-ROM to source directory you created.

For example, when creating a source directory to distribute Netfinity Manager Services for OS/2, copy all of the files from the OS2/SERVICES directory into the created directory.

To create a source directory for a Netfinity Manager installation:

1. Create a new directory on your system. This new directory will serve as a source directory for the program files.

Important:

Be sure to copy the Client Services for Netfinity Manager source files before the copying the Netfinity Manager source files because the Netfinity Manager directory contains some files that will overwrite files from the Client Services for Netfinity Manager directory.

Only Netfinity Manager installations can be done from this directory.

2. Copy the files from the appropriate Client Services for

Netfinity Manager directories.

For example, when creating a source directory to distribute Netfinity Manager for OS/2, copy all of the files from the OS2/SERVICES directory into the source directory.

3. Copy the files from the appropriate Netfinity Manager directory.

For example, when creating a source directory to distribute Netfinity Manager for OS/2, copy all of the files from the OS2/MANAGER directory into the source directory.

After an installation source directory has been created, use a response file and the Netfinity Manager installation pro-

Netfinity Manager

141

gram command-line parameters. The Netfinity Manager installation program supports the following command-line parameters:

/R:

drive+path+filename

Specifies the drive, path, and file name of the response file. See the NETFBASE.RSP file (located in the directory in which Netfinity Manager was installed) for an example of a response file with comments on the included parameters.

/S:

drive+path

Specifies the drive and path to install

from

. This is the directory to which the files were copied.

/T:

drive

Specifies the drive to install

to

. Default is the current startup drive.

/TU:

drive+path

Specifies the drive and path of the CONFIG.SYS file to update. The default is to change the CONFIG.SYS in the root directory of the drive specified in the /T parameter (or the startup drive). This parameter is ignored if the

ChangeConfig

parameter in the response file is

FALSE.

For example, the line:

NETFINST /R:NETFBASE.RSP /S:Y:\NETFIN

/T:C /TU:D:\ will install Netfinity Manager, using the options in the response file NETFBASE.RSP, from the directory

Y:\NETFIN, to drive C: (the directory to which the files are installed is taken from the response file), and will modify the CONFIG.SYS file in the D:\ directory.

Note: For information on how to use a CID-enabled software distribution manager, refer to the publications provided with the individual CID-enabled product.

Customized installation

For security reasons, not all users might need to have access to all services. User access can be restricted by creating a customized installation that will prevent some services from being installed.

To create a customized installation, the INSTALL.INI file must be edited. For example, when creating a customized

Netfinity Manager for Windows 95 or NT installation, edit the

INSTALL.INI file that is found on Netfinity Manager directory.

The INSTALL.INI file has three sections, separated by the line

[==]

The first section contains the installation configuration that can be selected during installation. There can be no more than eight choices. Each choice takes up two lines. The first line is the text that is displayed next to the installation configuration radio button. The second line is a list of the options in the third section that will be installed when this choice is selected for installation.

142


For example:

;IBM SysMgt Install Script, Version 2 (Do not remove this comment line)

Netfinity Manager Installation [Manager 16900]

Advanced System Management Support [ServProc 450]

Capacity Manager Enhancement [CapMgt 5600]

Remote Workstation Control [RWC 2000]

World Wide Web Enhancement (TCPIP Required)

[WebManager 3000] IsTcpip

[==]

Netfinity Manager CD for Windows 95/NT

[==]

NetFinity Admin

NULL Manager

CL 0 1 NETFBASE.EXE

CCL 0 1 NETDOM.INI

CCL 0 1 NETNODES.INI

CCL 0 1 INSTALL.BAT

CCL 0 1 NETFINST.EXE

CCL 0 1 INSTALL.INI

CCL 0 1 WININST.HLP

CL 0 1 APCKINST.DLL

;Screen Capture GUI

;NULL Manager

; CL 0 1 SAVEG.EXE

; CL 0 1 SAVEG.HLP

This INSTALL.INI will create a Netfinity Manager installation configuration that also installs Advanced System Management, Capacity Manager, Remote Workstation Control, and

Netfinity Manager World Wide Web enhancement.

The second section contains the names of the CD that this installation script will use.

The third section contains the list of options that can be installed. These are the options that are selected by the choices in the first section. The options are consecutively numbered starting at 1, so any inserted options will change the number of all following options. Each option uses the following format:

Option Name

Dll-entrypoint option file option file

...

install command install command

...

Option Name

An identifying comment by the installation program. All options must have a different Option Name. This is used only for identification.

Netfinity Manager

143

Dll-entrypoint

Used to determine whether an option is valid for a given target machine. In most cases, it should be the reserved string "NULL."

The easiest way to customize an installation is to simply put a semicolon in front of any service that you want to remove from the installation.

To add a line item in a specific section, add all the necessary item information in the format shown in the following example.

Before:

Screen Capture GUI

NULL Manager

CL 0 1 SAVEG.EXE

CL 0 1 SAVEG.HLP

After:

Screen Capture GUI

NULL Manager

CL 0 1 SAVEG.EXE

CL 0 1 SAVEG.HLP

CL 0 1 CUSTOM.INI

144


FRU information (service only)

Field Replacement Units (FRUs) should be replaced by qualified service personnel only.

LED switch card

Before you begin:

•

Read “Safety information” on page 196.

•


63.

88

Þ

1Ý

Þ

2Ý

Holding screws

LED switch card

To remove the LED switch card, do the following:

1. Power-off the server, if it is on.

2. Unplug the server.


4. Disconnect the switch card cables.

5. Remove the 4 holding screws.

6. Lift the switch card out of the server.

145

Four-fan housing


•


•


63.

Þ

1Ý

Þ

2Ý

Release latches

Fan housing

To remove the four-fan housing, do the following:




4. Remove the four fan assemblies.

5. Remove all adapters from the Active PCI adapter slots.

6. Remove the plastic dividers between the PCI adapter slots.

7. Press the fan assembly release latches on both sides of the fan assembly; then, remove the fan assembly from the server.

146


Dual fan mount assembly with cable


•


•


63.

Note: To remove the fan housing assembly with card guides

(for four fans), see step 4 on page 72.

88

Þ

1Ý

Þ

2Ý

Holding screws

Dual fan mount assembly

To remove the dual fan mount assembly with cable, do the following:




4. Disconnect the dual fan mount cable.

5. Remove the two holding screws.

6. Gently lift the fan mount assembly out of the server.

FRU information (service only)

147

Service processor card assembly


•


•


63.

88

Þ

1Ý

Þ

2Ý

Holding screws

Service processor card assembly

To remove the service processor card assembly, do the following:




4. Remove the dual fan mount assembly (see “Dual fan mount assembly with cable” on page 147).

5. Remove the two holding screws.

6. Gently lift the service processor card away from the system board and out of the server.

148


PCI switch card


•


•


63.

Þ

1Ý

Switch card latches

Þ

2Ý

Switch card assembly


2. Disconnect the server from the electrical outlet.


4. Disconnect the switch card cable from the system board.

5. Disengage the switch card: a. Press the switch card latches toward the front and sides of the server.

b. Push the latches through the notches.

6. When the switch card latches have been disengaged from the notches, gently pull the switch card free and lift it up and out of the server.

Note: You may have to tilt the top of the switch card toward the front of the server when removing it.

7. To replace the switch card, reverse the steps above.


149

Power backplane assembly


•


•


63.

Þ

1Ý

Þ

2Ý

Holding screws

Power backplane

To remove the power backplane assembly, do the following:




4. Remove the system board assembly (see “System board assembly with backerplate” on page 151).

5. Disconnect all cables to the power backplane.

6. Remove the three holding screws.

7. Lift the power backplane out of the server.

150


System board assembly with backerplate


•


•


63.

88

Þ

1Ý

Þ

2Ý

Þ

3Ý

Shipping screws

Release latch assembly

System board assembly

To remove the system board assembly with backerplate, do the following:




4. Remove the four fan assemblies.

5. Remove the four-fan housing (see “Four-fan housing” on page 146).

6. Disconnect cables on the system board.

7. Remove the memory card.

8. Remove all microprocessors.

9. Remove the shipping screw on each side of the server.

10. Engage the release latch assembly: a. Press in on the release button on each side of the server at the same time.

b. Push each of the two release latches at the same time toward the rear of the server


151

11. Gently lift the system board assembly out of the server.

12. Reverse the above steps to connect the system board assembly.

Note: Shipping screws do not have to be replaced for the server to function.

152


Symptom-to-FRU index

This index supports Netfinity 6000R – Type 8682 servers.

Notes:

1. Check the configuration before you replace a FRU.

Configuration problems can cause false errors and symptoms.

2. The default configuration can be loaded by starting the system and then pressing the reset button four times, waiting 15 seconds between each press. Once the configuration has reset to the default, it must be saved in Setup to be stored in CMOS.

3. For IBM devices not supported by index, refer to the manual for that device.

4. Always start with “General checkout” on page 1.

The Symptom-to-FRU lists symptoms, errors, and the possible causes. The most likely cause is listed first. Use this

Symptom-to-FRU index to help you decide which FRUs to have available when servicing the computer. The POST

BIOS displays POST error codes and messages on the screen.

Beep symptoms

Beep symptoms are short tones or a series of short tones separated by pauses (intervals without sound). See the following examples.

Note: One beep after successfully completing POST indicates the system is functioning properly.

Beeps

1-2-3

4

Description

• One beep

• A pause (or break)

• Two beeps

• A pause (or break)

• Three Beeps

Four continuous beeps

Beep/Symptom

1-1-3

(CMOS write/read test failed)

1-1-4

(BIOS EEPROM checksum failed)

FRU/Action

1. Battery

2. System Board

1. System Board

153

1-4-3

(Interrupt vector loading test failed)

2-1-1

(Secondary

DMA register failed)

2-1-2

(Primary DMA register failed)

2-1-3

(Primary interrupt mask register failed)

2-1-4

(Secondary interrupt mask register failed)

2-2-1

(Interrupt vector loading failed)

2-2-2

(Keyboard controller failed)

Beep/Symptom

1-2-1

(Programmable

Interval Timer failed)

1-2-2

(DMA initialization failed)

1-2-3

(DMA page register write/read failed)

1-2-4

(RAM refresh verification failed)

1-3-1

(1st 64K RAM test failed)

1-3-2

(1st 64K RAM parity test failed)

FRU/Action

1. System Board

1. System Board

1. System Board

1. DIMM

2. System Board

3. Memory Card

1. DIMM

2. Memory Card

3. System Board

1. DIMM

2. Memory Card

3. System Board

1. System Board

1. System Board

1. System Board

1. System Board

1. System Board

1. System Board

1. System Board

2. Keyboard

154


Beep/Symptom

2-2-3

(CMOS power failure and checksum checks failed)

2-2-4

(CMOS configuration info validation failed)

2-3-1

(Screen initialization failed)

2-3-2

(Screen memory failed)

2-3-3

(Screen retrace failed)

2-3-4

(Search for video ROM failed)

2-4-1

(Video failed, screen believed operable)

3-1-1

(Timer tick interrupt failed)

3-1-2

(Interval timer channel 2 failed)

3-1-3

(RAM test failed above address

OFFFF h))

3-1-4

(Time-Of-Day clock failed)

3-2-1

(Serial port failed)

3-2-2

(Parallel port failed)

FRU/Action

1. Battery

2. System board

1. Battery

2. System board

1. System Board

1. System board

1. System board

1. System board

1. System board

1. System Board

1. System Board

1. DIMM

2. Memory card

3. System board

1. Battery

2. System Board

1. System board

1. System board

Symptom-to-FRU index

155

Beep/Symptom

3-2-3

(Math coprocessor failed)

3-2-4

(Failure comparing

CMOS memory size against actual)

3-3-1

(Memory size mismatch occurred, see

"Memory

Settings" on

page 47)

3-3-2

(Critical SMBUS error occurred)

(I2C bus error)

Two Short

Beeps

(Information only, the configuration has changed)

Three Short

Beeps

One

Continuous

Beep

FRU/Action

1. Optional processor (if

installed)

2. Processor

3. System board

1. DIMM

2. Battery

3. System board

1. DIMM

2. System board

3. Battery

3-3-3

(No operational memory in system)

1. Disconnect the server power

cord from outlet, wait 30 seconds and retry.

2. System Board

3. DIMMs

4. Memory Card

5. DASD Backplane

6. Power Supply

7. Power Supply Backplane

8. 12C Cable

1. Install or reseat the memory

modules, then do a 3 boot

reset. (See “Using the

Configuration/Setup Utility program” on page 43.)

2. DIMMs

3. Memory Card

4. System Board

1. Run Diagnostics

2. Run Configuration/Setup

1. DIMM

2. System Board

1. Processor

2. Optional Processor (if installed)

3. System Board

4. Service Processor Card

156


Beep/Symptom

Repeating

Short Beeps

One Long and

One Short Beep

One Long and

Two Short

Beeps

Two Long and

Two Short

Beeps

FRU/Action

1. Keyboard

2. System Board

1. Video adapter (if present)

2. System Board

1. Video adapter (if present)

2. System Board

1. Video adapter

No beep symptoms

No Beep

Symptom

No beep and the system operates correctly.

No Beeps occur after successfully completing

POST (The

Power-On

Status is disabled.)

No ac power

(Power supply ac LED is off)

FRU/Action

1. Diagnostic LED Panel

1. Run Configuration/Setup, set the

Start Options Power-On Status to enable.

2. Diagnostic LED Panel

3. System Board

No beep and no video

System will

not power-up

(Power supply ac LED is on)

1. Check the power cord.

2. Power Supply (If two are installed, swap them to determine if one is defective.)

3. Power Backplane

1. See “Undetermined problems”

on page 186

1. See“Power supply LED errors”

on page 170

Diagnostic panel error LEDs

The system error LED is turned on when an error is detected. If the system error LED is on, remove the cover


157

and check the diagnostic panel LEDs. The following is a complete list of diagnostic panel LEDs followed by the

FRU/Action for correcting the problem.

Note: If a diagnostic panel LED is on and the information

LED panel system error LED is off, there is probably an LED problem. Run LED diagnostics.

Notes:

1. To locate the LEDs on the system board see “System board component locations” on page 54.

2. Check the System Error Log for additional information before replacing a FRU.

3. It may be necessary to view the System Error Log from a remote connection, such as MOST.

4. The memory card DIMM error LEDs and processor error LEDs turn off when the system is powered down.

Note: The System Error LED will also be on.

Diagnostic

Panel LED

All LEDs off

(Check System

Error Log for error condition, then clear

System Error

Log when the problem is found.)

CPU LED on

(The LED next to the failing

CPU should be on.)

DASD LED on

(Check amber drive LED for a failing hard drive if RAID system.)

FAN LED on

FRU/Action

1. System Error Log is 75% full;

clear the log.

2. Bad, missing or mis-installed processor terminator; remove and reinsert terminator.

3. PFA alert; check Netfinity log for failure; clear PFA alert; remove

AC power for at least 20 seconds, reconnect, then power up system.

4. Run Information Panel diagnostics.

1. Insure terminator (or processor

if multiprocessor system) is

installed in slot D. See

“Installing a microprocessor kit” on page 81.

2. Processor 1, 2, 3, or 4

3. System Board.

1. Be sure the fans are operating

correctly and the air flow is good.

2. Failing drive.

3. SCSI Backplane.

MEM LED on

(The LED next to the failing

DIMM is on.)

1. Check individual fan LEDs.

2. Replace respective fan.

3. Fan Cable.

4. System Board.

5. Power Backplane Board.

1. Failing DIMM(s) in slot J1-J16.

2. Memory Card.

3. System Board.

158



Diagnostic

Panel LED

FRU/Action

NMI LED on

Note: NMI LED can only be turned off by removing ac power from system, then restoring ac power.

PCI A LED on

1. Reboot the system.

2. Check the System Error Log.

PCI B LED on

1. Check System Error Log for

additional information.

2. PCI card in slot 1. See “System board component locations” on page 54.

3. Remove all PCI adapters from slots 1-6.

4. Replace failing PCI adapter.

5. System Board.



2. PCI card in slots 2-4. See

“System board component locations” on page 54.



5. System Board.

PCI C LED on



2. PCI card in slots 5-6. See

“System board component locations” on page 54.



5. System Board.

PS1 LED on

PS2 LED on

1. Check the DC Good LED on

power supply 1. If off, replace power supply 1.

2. Power Backplane.



2. Power Backplane.


159


Diagnostic

Panel LED

FRU/Action

PS3 LED on



2. Power Backplane.

SP Bus on

Event Log

Non Red

TEMP LED on

1. SP Bus card.

2. System Board.


1. Check PS1, PS2, and PS3 LEDs

and take the actions for those indicators.

2. See “Diagnostic panel error LEDs” on page 157.

1. Ambient temperature must be

within normal operating

specifications. See “Features and specifications” on page 3.

2. Ensure fans are operating correctly.

3. Examine System Error Log. a. DASD over recommended temperature (DASD LED also on)

(1) Overheating hard drive

(2) DASD Backplane

(3) System Board b. System over recommended temperature for CPU X

(where X is CPU 1, 2, 3, or 4)

(CPU LED also on)

(1) CPU X

Diagnostic error codes

Note: In the following error codes, if

XXX

is

000

,

195

, or

197

do not replace a FRU. The description for these error codes are:

000

195

The test passed.

The Esc key was pressed to abort the test.

197

This is a warning error and may not indicate a hardware failure.

For all error codes, replace/follow the FRU/Action indicated.

160


Error

Code/Symptom

001-XXX-000

(Failed core tests)

001-XXX-001

(Failed core tests)

001-250-000

(Failed System

Board ECC)

001-250-001

(Failed System

Board ECC)

005-XXX-000

(Failed Video test)

011-XXX-000

(Failed COM1

Serial Port test)

011-XXX-001

(Failed COM2

Serial Port test)

014-XXX-000

(Failed Parallel

Port test)

015-XXX-001

(Failed USB test)

015-XXX-015

(Failed USB

External Loopback test)

015-XXX-198

(USB device connected during

USB test)

FRU/Action

1. System Board

1. System Board

1. System Board

1. System Board

1. Video Adapter (if installed)

2. System Board

1. System Board

1. System Board

1. System Board

1. System Board.

1. Make sure parallel port is not disabled.

2. Re-run USB External

Loopback test.

3. System board.

1. Remove USB devices from

USB1 and USB2.

2. Re-run test.

3. System Board.

1. System Board 020-XXX-000

(Failed PCI

Interface test)

020-XXX-001

(Failed Hot-Swap

Slot 1 PCI Latch test)

020-XXX-002

(Failed Hot-Swap


1. PCI Hot-Swap Latch

Assembly

2. System Board


Assembly

2. System Board


161

Error

Code/Symptom

020-XXX-003

(Failed Hot-Swap


FRU/Action


Assembly

2. System Board

020-XXX-004

(Failed Hot-Swap


020-XXX-005

(Failed Hot-Swap


020-XXX-006

(Failed Hot-Swap



Assembly

2. System Board


Assembly

2. System Board


Assembly

2. System Board

030-XXX-000

(Failed Internal

SCSI interface test)

1. System Board

030-XXX-00N

(Failed SCSI test on PCI slot N.

Check system error log before replacing a FRU.)

1. Adapter in Slot N

035-XXX-099

1. No adapters were found.

2. If adapter is installed re-check connection.

1. Adapter

2. SCSI Backplane

3. Cable

035-XXX-S99

(Failed RAID test on PCI slot S. S = number of failing

PCI slot. Check

System Error Log before replacing a

FRU.)

035-XXX-SNN

(Check System

Error Log before replacing a FRU.

S = number of failing PCI slot; NN

= SCSI ID of failing fixed disk.)

1. Fixed Disk with SCSI ID NN

on RAID adapter in PCI slot

S.

162


Error

Code/Symptom

035-253-S99

(RAID adapter initialization failure)

075-XXX-000

(Failed Power

Supply test)

089-XXX-001

(Failed

Microprocessor test)

089-XXX-002

(Failed Optional


089-XXX-003

(Failed Optional


089-XXX-004

(Failed Optional


165-XXX-000

(Failed Service

Processor test)

FRU/Action

1. ServeRAID Adapter in slot S

is not configured properly.

Obtain the basic and extended configuration status and refer to the ServeRAID Hardware

Maintenance Manual for more information.

2. Cable

3. SCSI Backplane

4. Adapter

1. Power Supply

1. Microprocessor

1. Optional Microprocessor 2



1. Service Processor Board.

2. System Board. Before replacing the System Board, ensure that System Board jumper J5 is not installed (the default) when the error occurs.

1. Run Diagnostic LED test for

the failing LED.

180-XXX-000

(Diagnostics LED failure)

180-XXX-001

(Failed information

LED panel test)

180-XXX-002

(Failed Diagnostics

LED Panel test)

180-XXX-003

(Failed System

Board LED test)

1. Information LED Panel

2. Diagnostic LED Panel

3. System Board

1. Diagnostics LED Panel

2. System Board

1. System Board


163

Error

Code/Symptom

180-XXX-004

(Failed Processor

LED test)

180-XXX-005

(Failed SCSI

Backplane LED test)

180-XXX-006

(Memory Board

LED test)

201-XXX-0NN

(Failed Memory test, see "Memory

Settings" on page

47.) NN = DIMM

location.

201-XXX-999

(Multiple DIMM failure, see error text.)

202-XXX-001

(Failed System

Cache test)

202-XXX-002

(Failed System

Cache test)

202-XXX-003

(Failed System

Cache test)

202-XXX-004

(Failed System

Cache test)

206-XXX-000

(Failed Diskette

Drive test)

FRU/Action

1. System Board

1. SCSI Backplane

2. SCSI Backplane Cable

3. System Board

1. Memory Board

2. System Board

1. DIMM Location J1-J16

2. Memory card

1. See error text for failing

DIMMs

2. Memory card

1. Microprocessor CPU 1




215-XXX-000

(Failed IDE CD-

ROM test)

217-XXX-000

(Failed BIOS Fixed

Disk test)

Note: If RAID is configured, the fixed disk number refers to the

RAID logical array.

1. Cable

2. Diskette Drive

3. System Board

1. CD-ROM Drive Cables

2. CD-ROM Drive

3. System Board

1. Fixed Disk 1

164


Error

Code/Symptom

217-XXX-001

(Failed BIOS Fixed

Disk test)


RAID logical array.

217-XXX-002

(Failed BIOS Fixed

Disk test)


RAID logical array.

217-XXX-003

(Failed BIOS Fixed

Disk test)


RAID logical array.

217-XXX-004

(Failed BIOS Fixed

Disk test)


RAID logical array.

217-XXX-005

(Failed BIOS Fixed

Disk test)


RAID logical array.

FRU/Action

1. Fixed Disk 2

1. Fixed Disk 3

1. Fixed Disk 4

1. Fixed Disk 5

1. Fixed Disk 6


165

Error

Code/Symptom

264-XXX-0NN

(NN = SCSI ID of failing Tape Drive)

FRU/Action

1. Tape Cartridge, if user

executed the Read/Write

Tape Drive test (XXX = 256)

2. SCSI or power cable connected to the tape drive with SCSI ID NN

3. Tape drive with SCSI ID NN – refer to Help and Service

Information appendix of tape drive’s User Guide.

4. System Board or SCSI

Controller – run SCSI

Controller diagnostic to determine of SCSI bus is functioning properly.

1. See error messages/text in

the PC Doctor error log for detailed information on each individual tape drive error.

264-XXX-999

(Errors on multiple tape drives, see error text for more info)

301-XXX-000

(Failed Keyboard test)

405-XXX-000

(Failed Ethernet test on controller on the System

Board)

405-XXX-00N

(Failed Ethernet test on adapter in

PCI slot N)

415-XXX-000

(Failed Modem test)

1. Keyboard

1. Verify that Ethernet is not

disabled in BIOS.

2. System Board

1. Adapter in PCI slot N.

2. System Board

1. Cable

2. Modem

3. System Board

Error symptoms

General

CD is not working properly.

CD-ROM drive tray

is not working.

(The server must be powered-on.)

FRU/Action

1. Clean the CD.

2. Run CD-ROM diagnostics.

3. CD-ROM Drive

1. Insert the end of a paper

clip into the manual trayrelease opening.


3. CD-ROM Drive

166


General

CD-ROM drive is not recognized.

Power switch does not work and reset button does work.

FRU/Action

1. Run Configuration/Setup,

enable primary IDE channel.

2. Check cables and jumpers.

3. Check for correct device driver.


5. CD-ROM drive

6. System Board

1. Verify that the power-on

control jumper on J19 is on pins 1 and 2.

2. Power Switch Assembly

3. System Board

1. Make sure front panel is plugged in.

1. Make sure On/Off Reset panel is plugged in.

1. Make sure CD-ROM drive cable is plugged in.

Front panel is not plugged in.

On/Off Reset panel is not plugged in.

CD-ROM drive cable is not plugged in.

Diskette drive inuse light stays on, or the system bypasses the diskette drive, or the diskette drive does not work.

1. If there is a diskette in the

drive, verify that: a. The diskette drive is enabled in the

Configuration/Setup utility program.

b. The diskette is good and not damaged. (Try another diskette if you have one.) c. The diskette is inserted correctly in the drive.

d. The diskette contains the necessary files to start the server.

e. The software program is

OK.

f. Cable is installed correctly (proper orientation)

2. Run Diskette Drive

Diagnostics.

3. Cable

4. Diskette Drive

5. System Board


167

General

Monitor problems

(general). Some

IBM monitors have their own self-tests.

If you suspect a problem with the monitor, refer to the information that comes with the monitor for adjusting and testing instructions.

FRU/Action

1. Monitor

2. Run Video Diagnostics. If diagnostics pass, the problem may be a video driver.

3. Display Adapter / System

Board

Setup

Netfinity Setup and

Installation CD won’t start.

Action

• Be sure the server is supported; all Netfinity servers with a startable

(bootable) CD-ROM drive are supported.

• If the startup (boot) sequence settings have been altered, be sure the CD-ROM is first in the boot sequence.


ServeRAID program cannot view all installed drives - or - cannot install NOS.

The

Operating

System Installation






your

NOS CD.

Can't install NOS - option is grayed out.





168


Setup

Netfinity Setup and

Installation CD won’t start.

Action

• Be sure the server is supported; all Netfinity servers with a startable

(bootable) CD-ROM drive are supported.

• If the startup (boot) sequence settings have been altered, be sure the CD-ROM is first in the boot sequence.


ServeRAID program cannot view all installed drives - or - cannot install NOS.

The

Operating

System Installation






your

NOS CD.

Can't install NOS - option is grayed out.





TechConnect CD

Can't start

TechConnect CD.

Action

Be sure you're starting the CD on a system with Microsoft Windows installed.

Can't view publications from

TechConnect CD, or text is unreadable.

Be sure you have the Adobe reader installed (available from the

TechConnect CD).


169

Diskette Factory

CD

Get "time out" or

"Unknown host" errors

Action

Be sure you have access to the

Internet through FTP directly.

Power supply LED errors

Use the power supply LED information on the following page to troubleshoot power supply problems.

Note: The minimum configuration required for the DC Good light to come on is:

• Power Supply

• Power Backplane

• System Board (With pins 2 and 3 on J19 connected together to bypass the power switch; see

“System board component locations” on page

54.

AC

Good

LED

DC

Good

LED

Off Off

Description

No power to system or ac problem.

FRU/Action

1. Check ac power

to system.

2. Power Supply

170


AC

Good

LED

DC

Good

LED

On Off

On On

Description

Standby mode or dc problem.

FRU/Action

1. Move jumper on

J19 to pins 2-3 to bypass power control. If the DC

Good LED comes on, press

Ctrl+Alt+Delete.

Watch the screen for any POST errors. Check the

System Error Log for any listed problems.

If the system powers up with no errors: a. Diagnostic

LED panel

2. Remove the adapters and disconnect the cables and power connectors to all internal and external devices.

Power-on the system. If the DC

Good LED comes on, replace the adapters and devices one at a time until you isolate the problem.

3. Power Supply

4. Power Backplane

5. System Board

Power is OK.

N/A

POST error codes

In the following error codes,

X

can be any number or letter.

Error

Code/Symptom

062

(Three consecutive boot failures using the default configuration.)

FRU/Action

1. Run Configuration/Setup

2. Battery

3. System Board

4. Processor


171

Error

Code/Symptom

101, 102, 106

(System and processor error)

111

(Channel check error)

114

(Adapter read-only memory error)

129

(Internal cache error)

151

(Real time clock error)

161

(Real time clock battery error)

FRU/Action

1. System Board

1. Failing adapter

2. DIMM

3. System board

1. Failing adapter

2. Run diagnostics

1. Processor

2. Optional processor (if installed)

1. Run Diagnostics

2. Battery

3. System Board


2. Battery

3. System Board


2. Battery

3. Failing Device

4. System Board

162

(Device

Configuration Error)

Note: Be sure to load the default settings and any additional desired settings; then, save

the configuration.

163

(Real-Time Clock error)

164

(Memory configuration changed, see

"Memory Settings"

on page 47.)

175

(Hardware error)

176, 177, 178

(Security hardware error)


2. Battery

3. System Board


2. DIMM

3. Memory Card

4. System Board

1. System Board


2. System Board

172


Error

Code/Symptom

184

(Power-on password corrupted)

185

(Drive startup sequence information corrupted)

186

(Security hardware control logic failed)

187

(VPD serial number not set.)

188

(Bad EEPROM

CRC #2)

189

(Three attempts were made to access the server with invalid passwords)

201

(Memory test error, see "Memory

Settings" on page

47.) If the server

does not have the latest level of BIOS installed, update the BIOS to the latest level and run the diagnostic program again.

229

(Cache error)

FRU/Action


2. System Board


2. System Board


2. System Board

1. Set serial number in Setup

2. System Board


2. System Board

1. Run Configuration/Setup,

enter the administrator password

2. System Board.

1. Run memory diagnostics.

2. DIMM

3. Memory card

4. System Board

1. Processor

2. Optional Processor (if installed)


2. Disabled DIMM

289

(DIMM has been disabled by user or system, see

"Memory Settings"

on page 47.)

301

(Keyboard or keyboard controller error)

1. Keyboard

2. System Board


173

Error

Code/Symptom

303

(Keyboard controller error)

602

(Invalid diskette boot record)

604

(Diskette drive error)

662

(Diskette drive configuration error)

962

(Parallel port error)

11XX

(System board serial port 1 or 2 error)

1162

(Serial port configuration conflict)

FRU/Action

1. System Board

2. Keyboard

1. Diskette

2. Diskette Drive

3. Cable

4. System Board


and Diagnostics

2. Diskette Drive

3. Drive Cable

4. System Board


and Diagnostics

2. Diskette Drive

3. Drive Cable

4. System Board

1. Disconnect external cable

on parallel port.


3. System Board


on serial port.


3. System Board


on serial port


3. System board

1. Processor

1200

(processor machine check)

1301

(cable to front panel not found)

1302

(cable from system board to power on and reset switches not found)

1. Cable

2. Front Panel


4. System Board

1. Cable


3. System Board

174


Error

Code/Symptom

1303

(cable from system board to power backplane not found)

1304

(cable to diagnostic

LED board not found)

1600

(Netfinity Advanced

System Management processor is not functioning) Do the following before replacing a FRU:

1. Ensure that a jumper is not installed on

J5.

2. Remove the ac power to the system, wait 20 seconds; then, re-connect the ac power.

Wait 30 seconds; then, power-on the system.

FRU/Action

1. Cable

2. Power Backplane

3. System Board

1. Cable

2. Diagnostic LED Board

3. System Board

1. System Board

2. Service Processor Board


175

Error

Code/Symptom

1601

(The system is able to communicate to the Service

Processor, but the

Service Processor failed to respond at the start of POST.)

Do the following before replacing a

FRU:

1. Remove the ac power to the system, wait 20 seconds; then, re-connect the ac power.

Wait 30 seconds; then, power-on the system.

2. Flash update the Service

Processor.

1800

(No more hardware interrupt available for PCI adapter)

1962

(Drive does not contain a valid boot sector)

2400

(Video controller test failure)

2462

(Video memory configuration error)

FRU/Action

1. System Board

2. Service Processor Board


2. Failing Adapter

3. System Board

1. Verify a bootable operating

system is installed.

2. If RAID system, refer to the

Hardware Maintenance

Manual for the specific RAID adapter.

3. Run Diagnostics

4. Hard Disk Drive

5. Cable

6. SCSI Backplane

7. System Board


2. System Board


2. System Board

176


Error

Code/Symptom

5962

(IDE CD-ROM configuration error)

FRU/Action


2. CD-ROM Drive

3. CD-ROM Power Cable

4. IDE Cable

5. System Board

6. Battery

1. Pointing Device

2. System Board

8603

(Pointing Device

Error)

00012000

(Processor machine check)

00019501

(Processor 1 is not functioning)

00019502


00019503


00019504


00019701

(Processor 1 failed

BIST)

00019702

(Processor 2 failed

BIST)

1. Update BIOS

2. Replace microprocessor

1. Processor 1

2. System Board

1. Processor 2

2. System Board

1. Processor 3

2. System Board

1. Processor 4

2. System Board

1. Processor 1

2. System Board

00019703

(Processor 3 failed

BIST)

00019704

(Processor 4 failed

BIST)

00180100

(No room for PCI option ROM)

00180200

(No more I/O space available for PCI adapter)

1. Processor 2

2. System Board

3. System Board

1. Processor 3

2. System Board

1. Processor 4

2. System Board


2. Failing Adapter

3. System Board


2. Failing Adapter

3. System Board


177

Error

Code/Symptom

00180300

(No more memory

(above 1MB for PCI adapter)

00180400

(No more memory

(below 1MB for PCI adapter)

00180500

(PCI option ROM checksum error)

00180600

(PCI device built-in self test failure)

FRU/Action


2. Failing Adapter

3. System Board


2. Failing Adapter

3. System Board

1. Remove Failing PCI Card

2. System Board

00180700

(

xxxxyyyy

planar

PCI device not responding (where

xxxx

is PCI vendor

ID and

yyyy

is PCI device ID)

00180800

(Unsupported PCI device installed)

00181000

(PCI error)


2. Failing Adapter

3. System Board

1. System Board

2. PCI Card

1. System Board

2. PCI Card

01295085

(ECC checking hardware test error)

01298001

(No update data for processor 1)

1. System Board

2. PCI Card

1. System Board

2. Processor

01298002


01298003


01298004


1. Ensure all processors are

the same stepping level and cache size.

2. Processor 1



2. Processor 2



2. Processor 3



2. Processor 4

178


Error

Code/Symptom

01298101

(Bad update data for processor 1)

01298102


FRU/Action



2. Processor 1



2. Processor 2

01298103


01298104




2. Processor 3



2. Processor 4


the same speed.

01298200

(Microprocessor speed mismatch)

I9990301

(Fixed boot sector error)

1. Hard Disk Drive

2. If RAID system, refer to the

Hardware Maintenance

Manual for the specific RAID adapter.

3. SCSI Backplane

4. Cable

5. System Board

1. Install operating system to

hard disk drive.

I9990305

(Fixed boot sector error, no operating system installed)

I9990650

(AC power has been restored)

Other numbers

1. Check cable

2. Check for interruption of power supply

3. Power Cable

Follow instructions on screen.

ServeRAID

For ServeRAID error codes and procedures, refer to the

Hardware Maintenance Manual for the particular RAID adapter in the system being serviced.


179

I2C bus fault messages

Message

Failure reading I2C device.

Check devices on bus 0.





Action

1. Reseat Service

Processor Board

2. Replace Service

Processor Board

3. Replace System Board

1. Reseat power supplies

2. Replace power supplies

3. Replace power backplane


1. Reseat front panel connectors

2. Replace front panel


1. Replace System Board Failure reading I2C device.








1. Reseat Service

Processor Board

2. Replace Service

Processor Board


1. Reseat CPUs

2. Replace CPUs


1. Reseat memory card

2. Replace memory card


1. Replace System Board Failure reading I2C device.






1. Replace SCSI backplane



1. Reseat DIMMs 1, 2, 3, and 4

2. Replace DIMMs 1, 2,

3, and 4



180


Message







Action

1. Reseat DIMMs 5, 6, 7l, and 8


7l, and 8



1. Reseat DIMMs 9, 10,

11, and 12


11, and 12



1. Reseat DIMMs 13, 14,

15, and 16

2. Replace DIMMs 13,

14, 15, and 16



SCSI error codes

Error Code

All SCSI Errors One or more of the following might be causing the problem:

• A failing SCSI device

(adapter, drive, controller)

• An improper SCSI configuration or SCSI termination jumper setting

• Duplicate SCSI IDs in the same SCSI chain

• A missing or improperly installed SCSI terminator

• A defective SCSI terminator

• An improperly installed cable

• A defective cable

FRU/Action

1. External SCSI

devices must be powered-on before you power-on the server.

2. The cables for all external SCSI devices are connected correctly.

3. If you have attached an external SCSI device to the server, make sure the external SCSI termination is set to automatic.

4. The last device in each SCSI chain is terminated correctly.

5. The SCSI devices are configured correctly.


181

Temperature error messages

Message

DASD "X" Over

Temperature (levelcritical; Direct Access

Storage Device bay "X" was over temperature)

DASD Over recommended

Temperature (sensor X)

(level-warning; the DASD backplane had an over temperature condition)

DASD under recommended

temperature (sensor X) level-warning; the DASD backplane had an under temperature condition)

Action

1. Ensure system is

being properly cooled;

see “Temperature checkout” on page 27.




CPU "X" over recommended

temperature (levelcritical; temperature of

CPU "X" reached critical level)

Power Supply "X"

Temperature Fault

(level-critical; power supply "x" had over temperature condition)

System over temperature for CPU

"X"

(level-warning; CPU "X" reporting over temperature condition)

System under recommended CPU "X"

temperature (levelwarning; system reporting under temperature condition for CPU "X")

1. Ambient temperature

must be within normal operating

specifications; (see

“Features and specifications” on page

3).




2. Replace CPU "X".


being properly cooled;


2. Replace Power Supply

"X"


being properly cooled;


2. Replace system board.





3).

182


Message

System over recommended ambient temperature

(level-warning; ambient temperature too warm for safe system operation)

Action





3).

Fan error messages

Message

Fan "X" fault (levelcritical; fan "X" beyond recommended RPM range)

Action

1. Check connections to

fan "X"

2. Replace fan "X"

Power error messages

Message

Power supply "X" DC

good fault (level-critical; power good signal not detected for power supply

"X")

Power supply "X" fan fault

(level-critical; fan fault in power supply "X")

Power supply "X" fault

(level-critical; overcurrent condition exists)

Power supply "X" 12V

fault (level-critical; overcurrent condition detected)

Power supply "X" 3.3V

fault (level-critical; 3.3V power supply "X" had an error)

Power supply "X" 5V fault

(level-critical; 5V power supply "X" had an error)

Power supply current exceeded max spec value

(level-critical; current draw in system is over allowance for a single supply)

Action

1. Replace power

supply "X"

1. Replace power

supply "X"

1. See “Power

checkout” on page

23.

1. See “Power


23.

1. See “Power


23.

1. See “Power


23.

1. See “Power


23.


183

Message

Power Supply "X" fault

(level-critical; power supply

"X" has been removed or has encountered some other fault)

Power Supply "X" overvoltage fault

(level-critical)

Power Supply "X" AC power removed, early power-off warning

(level-critical; a power supply has been unplugged or has been installed without an ac cord)

System running non-

redundant power

(level-non-critical; system does not have redundant power)

Action

1. Check error log for

other messages.

2. See “Power checkout” on page 23.

1. See “Power


23.

1. Check to see if ac

cords are plugged in properly.

2. Problem may have been temporary ac problem. If problem

persists, see “Power checkout” on page

23.

1. Add another power

supply

2. Remove options from system

3. System can continue to operate without redundancy protection if 1 and 2 above are not followed.

1. Check connections

to power subsystem

2. Replace power supply


System under recommended voltage for

"X" v (level-warning; indicated voltage supply under nominal value; value for "X" can be +12, -12, or

+5)

System under recommended voltage on

3.3 v (level-warning; 3.3 volt supply under nominal value)

"X" V bus fault (levelcritical; overcurrent condition on "X" voltage bus)

12V "X" bus fault (levelcritical; overcurrent condition on 12 volt "X" voltage bus)

5V fault (level-critical; overcurrent condition on 5 V subsystem)

1. Check connections

to power subsystem



1. See “Power


23.

1. See “Power


23.

1. See “Power


23.

184


System shutdown

Refer to the following tables when experiencing system shutdown related to voltage or temperature problems.

Voltage related system shutdown

Message

System shutoff due to "X"

V over voltage (levelcritical; system shutoff due to "X" supply over voltage)

System shutoff due to "X"

V under voltage (levelcritical system shutoff due to "X" supply under voltage)

Action

1. Check power supply

connectors



1. Check power supply

connectors



Temperature related system shutdown

Message

System shutoff due to CPU

"X" over temperature

(level-critical; CPU "X" is over temperature)

System shutoff due to CPU

"X" under temperature

(level-critical; CPU "X" is under temperature)

System shutoff due to

DASD temperature (sensor

X) (level-critical; DASD area reported temperature outside recommended operating range)

System shutoff due to high

ambient temperature (levelcritical; high ambient temperature)

Action


being properly

cooled, see

“Temperature checkout” on page

27.

2. Replace CPU "X"

1. Ambient

temperature must be within normal operating

specifications (see

“Features and specifications” on page 3.

2.


being properly

cooled, see

“Temperature checkout” on page

27.

1. Ambient





185

Message

System shutoff due to faults on each supply

(level-critical; each installed power supply encountered a fault condition)

Action

1. See “Power


23.

DASD checkout

Message

Hard drive "X" removal

detected (level-critical; hard drive "X" has been removed)

Hard Drive (SCSI ID "X")

fault (level-critical; error has occurred on a DASD drive in a RAID configuration causing it to be defunct)

Action

1. Information only,

take action as appropriate.

1. Ambient




CPU checkout

Message

Host BIST fail (levelinformational; host’s built-in self test failed)

Internal Error CPU "X"

fault (level-critical; specified processor reported internal error and is held offline and system restarted)

Action

1. Reseat CPU

2. Replace CPU

1. If problem persists,

replace CPU "X".

Undetermined problems

You are here because the diagnostic tests did not identify the failure, the Devices List is incorrect, or the system is inoperative.

Note: A corrupt CMOS can cause undetermined problems.

Check the LEDs on all the power supplies, see“Power supply LED errors” on page 170. If the LEDs indicate the power

supplies are working correctly, return here and do the following:

1. Power-off the computer.

2. Be sure the system is cabled correctly.

186


3. Remove or disconnect the following (one at a time) until you find the failure (power-on the computer and reconfigure each time).

Any external devices

Surge suppressor device (on the computer)

Modem, printer, mouse, or non-IBM devices

Each adapter

Drives

Memory-Modules (Minimum requirement = 512

MB (4x128 MB DIMMs))

Note: Minimum operating requirements are: a. 1 Power Supply b. Power Backplane c. System Board (with pins 2 and 3 on J23 connected together to bypass the power switch; default is pins 1 and 2) d. 1 Microprocessor e. 1 Terminator Card in Slot 4 f. Memory Module (with a minimum of 1 bank of 128 MB DIMMs (128x4))

4. Power-on the computer. If the problem remains, suspect the following FRUs in the order listed:

Power Supply

Power Backplane

System Board

Notes:

1. If the problem goes away when you remove an adapter from the system, and replacing that adapter does not correct the problem, suspect the System Board.

2. If you suspect a networking problem and all the system tests pass, suspect a network cabling problem external to the system.


187

188


Parts listing

20

19

18

88

17

16

15

14

13

12

2

3

4

1

5

6

7

8

9

10

11

189

System

Index

1

2

3

4

5

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

System (Netfinity 6000R – Type

8682) Models 1RY, 2RY

Top cover assembly (Models 1RY,

2RY)

Memory card with backer plate assembly (Models 1RY, 2RY)

CPU terminator card, slot 2

(Model 1RY)

92mm x 38 fan assembly

(Models 1RY, 2RY)

700MHz/1MB processor (Model

1RY)

700MHz/2MB processor (Model

2RY)

92mm fan housing assembly with card guides (Models 1RY, 2RY)

LED/switch card (katana) (Models

1RY, 2RY)

SCSI backplane with backerplate assembly (Models 1RY, 2RY)

Slim hard disk drive bezel filler assembly (Models 1RY, 2RY)

Power supply filler panel (Models

1RY, 2RY)

1.44MB diskette drive (Models

1RY, 2RY)

Front bezel assembly, 18mm

(Models 1RY, 2RY)

40x CD-ROM (Models 1RY, 2RY)

Power supply with mounting,

270w (Models 1RY, 2RY)

Frame assembly (chassis)

(Models 1RY, 2RY)

Power backplane assembly

(Models 1RY, 2RY)

System board and backerplate assembly (Models 1RY, 2RY)

Service processor card assembly

(Models 1RY, 2RY)

120mm fan dual fan mount with cable assembly (Models 1RY,

2RY)

120mm fan assembly (Models

1RY, 2RY)

Rails snap-on, CD-ROM (Models

1RY, 2RY)

Slide assembly, FDD left/right

(Models 1RY, 2RY)

190


FRU No.

36L9611

00N6637

94H0598

37L0305

19K0911

19K0913

00N8981

37L6460

00N8953

00N7259

37L0331

76H4091

00N8971

09N0881

37L0311

36L9590

00N6651

00N6623

00N6644

09N7936

09N7938

00N6412

00N6413

Index



Assembly, 3u left EIA flange

(Models 1RY, 2RY)

Assembly, 3u right EIA flange

(Models 1RY, 2RY)

Miscellaneous rack hardware kit

(clips (12), cage nuts (12), M6 screws (12), M4x5 screws (10),

Velcro strips (10)) (Models 1RY,

2RY)

Slide with brackets assembly

(Models 1RY, 2RY)

Rigid cable management arm

(Models 1RY, 2RY)

Miscellaneous plastics kit

(memory card support guides (2), processor support goalposts (2),

DASD backplane locking latch

(1), fan housing locking latch (1))

(Models 1RY, 2RY)

Cassette, handle, slot 2 terminator card (Models 1RY,

2RY)

Label, system service (Models

1RY, 2RY)

PCI hot plug switch card/housing

(Models 1RY, 2RY)

128 MB memory (Models 1RY,

2RY)

AC distribution box assembly

(Models 1RY, 2RY)


2RY)


2RY)


2RY)

Cable, signal I2C - I/O planar to

SCSI backplane ( 2x7) (Models

1RY, 2RY)

Cable, signal lvd-SCSI - repeater to SCSI backplane (Models 1RY,

2RY)

Cable, SCSI to bulkhead (Models

1RY, 2RY)

Cable, 2 drop 120mm fan

(Models 1RY, 2RY)

Cable, 50 circuit signal with connector (Models 1RY, 2RY)

Cable, 34 circuit FDD w / connector (Models 1RY, 2RY)

FRU No.

00N7190

00N7192

00N7193

00N7205

00N7211

00N8961

10L6936

00N7198

09N7762

09N7945

09N7947

09N7949

36L9586

00N6665

33L3114

00N8955

33L3120

33L3116

33L3118

00N7185

Parts listing

191

Index



Cable, power - power backplane to SCSI backplane & devices (4 drop) (Models 1RY, 2RY)

Cable, signal - planar to CD-ROM

(ide) (Models 1RY, 2RY)

Cable, power 24 circuit (power backplane - planar) (Models 1RY,

2RY)

Cable, power - signal - power backplane to I/O planar 2x17

(Models 1RY, 2RY)

Cable, power - I/O planar to fans

2x15 (5 drop) (Models 1RY, 2RY)

Cable, signal planar to SCSI backplane (Models 1RY, 2RY)

FRU No.

36L9601

36L9603

36L9605

36L9609

36L9613

37L0350

Keyboards

Keyboard

US English

French Canadian

LA Spanish

Arabic

Belgium/French

Belgium/UK

Bulgarian

Czech

Danish

Dutch

French

German

Greek

Hebrew

Hungarian

Korean

Iceland

Italy

Norwegian

Polish

Portugese

Romanian

Russian

Serbian/Cyrillic

Slovic

Spanish

Swedish/Finn

Swiss, F/G

Turkish

192


02K0901

37L2567

37L2568

37L2569

37L2570

37L2571

37L2572

37L2573

37L2574

37L2575

37L2576

37L2577

37L2578

37L2579

FRU No.

37L2551

37L2552

37L2553

37L2555

37L2556

37L2557

37L2558

37L2559

37L2560

37L2561

37L2562

37L2563

37L2564

37L2565

37L2566

Keyboard

Turkish

UK English

Yugosl/Lat

US English-EMEA

Chinese/US

Thailand

French Canadian

FRU No.

37L2580

37L2581

37L2582

37L2583

37L2585

37L2587

37L0913

Power cords

Power cord

China (PRC)

Japan

Thailand

Israel

Bangladesh, Burma, India, Pakistan,

South Africa, Sri Lanka

Chile, Ethiopia, Italy, Libya, Somalia

Argentina, Australia, New Zealand, Papua

New Guinea, Paraguay, Uruguay, Western

Samoa

Antigua, Bahrain, Brunei, Channel

Islands, Cyprus, Dubai, Fiji, Ghana, Hong

Kong, Iraq, Ireland, Kenya, Kuwait,

Malawi, Malaysia, Malta, Nepal, Nigeria,

Polynesia, Qatar, Sierra Leone,

Singapore, Tanzania, Uganda, United

Kingdom, Yemen, Zambia

Afghanistan, Algeria, Andorra, Angola,

Austria, Belgium, Benin, Bulgaria, Burkina

Faso, Burundi, Cameroon, Central African

Rep., Chad, Czech Republic, Egypt,

Finland, France, French Guiana,

Germany, Greece, Guinea, Hungary,

Iceland, Indonesia, Iran, Ivory Coast,

Jordan, Lebanon, Luxembourg, Macau,

Malagasy, Mali, Martinique, Mauritania,

Mauritius, Monaco, Morocco,

Mozambique, Netherlands, New

Caledonia, Niger, Norway, Poland,

Portugal, Romania, Senegal, Slovakia,

Spain, Sudan, Sweden, Syria, Togo,

Tunisia, Turkey, former USSR, Vietnam, former Yugoslavia, Zaire, Zimbabwe

Denmark, Switzerland, Liechtenstein

FRU No.

01K9851

01K9853

12J5120

12J5122

12J5124

12J5126

12J5128

12J5987

55H6643

55H6646

Parts listing

193

Power cord

Bahamas, Barbados, Bermuda, Bolivia,

Brazil, Canada, Cayman Islands,

Colombia, Costa Rica, Dominican

Republic, Ecuador, El Salvador,

Guatemala, Guyana, Haiti, Honduras,

Jamaica, Korea (South), Liberia, Mexico,

Netherlands Antilles, Nicaragua, Panama,

Peru, Philippines, Saudi Arabia,

Suriname, Taiwan, Trinidad (West Indies),

Venezuela

United States of America

FRU No.

76H4865

6952301

(110)

1838574

(220)

36L8886

(220V/15A)

194


Related service information

Note: The service procedures are designed to help you isolate problems. They are written with the assumption that you have model-specific training on all computers, or that are familiar with the computers, functions, terminology, and service information provided in this manual.

195

Safety information

The following section contains the safety information that you need to be familiar with before servicing an IBM mobile computer.

General safety

Follow these rules to ensure general safety:

• Observe good housekeeping in the area of the machines during and after maintenance.

• When lifting any heavy object:

1. Ensure you can stand safely without slipping.

2. Distribute the weight of the object equally between your feet.

3. Use a slow lifting force. Never move suddenly or twist when you attempt to lift.

4. Lift by standing or by pushing up with your leg muscles; this action removes the strain from the muscles in your back.

Do not attempt to lift any objects that weigh more than 16 kg (35 lb) or objects that you think are too heavy for you.

• Do not perform any action that causes hazards to the customer, or that makes the equipment unsafe.

• Before you start the machine, ensure that other service representatives and the customer's personnel are not in a hazardous position.

• Place removed covers and other parts in a safe place, away from all personnel, while you are servicing the machine.

• Keep your tool case away from walk areas so that other people will not trip over it.

• Do not wear loose clothing that can be trapped in the moving parts of a machine. Ensure that your sleeves are fastened or rolled up above your elbows. If your hair is long, fasten it.

• Insert the ends of your necktie or scarf inside clothing or fasten it with a nonconductive clip, approximately 8 centimeters (3 inches) from the end.

• Do not wear jewelry, chains, metal-frame eyeglasses, or metal fasteners for your clothing.

Remember: Metal objects are good electrical conductors.

• Wear safety glasses when you are: hammering, drilling soldering, cutting wire, attaching springs, using solvents, or working in any other conditions that might be hazardous to your eyes.

• After service, reinstall all safety shields, guards, labels, and ground wires. Replace any safety device that is worn or defective.

• Reinstall all covers correctly before returning the machine to the customer.

196


Electrical safety

CAUTION:

Electrical current from power, telephone, and communication cables can be hazardous. To avoid personal injury or equipment damage, disconnect the attached power cords, telecommunication systems, networks, and modems before you open the server covers, unless instructed otherwise in the installation and configuration procedures.

Observe the following rules when working on electrical equipment.

Important: Use only approved tools and test equipment.

Some hand tools have handles covered with a soft material that does not insulate you when working with live electrical currents.

Many customers have, near their equipment, rubber floor mats that contain small conductive fibers to decrease electrostatic discharges. Do not use this type of mat to protect yourself from electrical shock.

• Find the room emergency power-off (EPO) switch, disconnecting switch, or electrical outlet. If an electrical accident occurs, you can then operate the switch or unplug the power cord quickly.

• Do not work alone under hazardous conditions or near equipment that has hazardous voltages.

• Disconnect all power before:

— Performing a mechanical inspection

— Working near power supplies

— Removing or installing main units

• Before you start to work on the machine, unplug the power cord. If you cannot unplug it, ask the customer to power-off the wall box that supplies power to the machine and to lock the wall box in the off position.

• If you need to work on a machine that has exposed electrical circuits, observe the following precautions:

— Ensure that another person, familiar with the power-off controls, is near you.

Remember: Another person must be there to switch off the power, if necessary.

— Use only one hand when working with poweredon electrical equipment; keep the other hand in your pocket or behind your back.

Remember: There must be a complete circuit to cause electrical shock. By observing the above rule, you may prevent a current from passing through your body.

Related service information

197

— When using testers, set the controls correctly and use the approved probe leads and accessories for that tester.

— Stand on suitable rubber mats (obtained locally, if necessary) to insulate you from grounds such as metal floor strips and machine frames.

Observe the special safety precautions when you work with very high voltages; these instructions are in the safety sections of maintenance information. Use extreme care when measuring high voltages.

• Regularly inspect and maintain your electrical hand tools for safe operational condition.

• Do not use worn or broken tools and testers.

•

Never assume

that power has been disconnected from a circuit. First,

check

that it has been powered-off.

• Always look carefully for possible hazards in your work area. Examples of these hazards are moist floors, nongrounded power extension cables, power surges, and missing safety grounds.

• Do not touch live electrical circuits with the reflective surface of a plastic dental mirror. The surface is conductive; such touching can cause personal injury and machine damage.

• Do not service the following parts with the power on when they are removed from their normal operating places in a machine:

— Power supply units

— Pumps

— Blowers and fans

— Motor generators and similar units. (This practice ensures correct grounding of the units.)

• If an electrical accident occurs:

— Use caution; do not become a victim yourself.

— Switch off power.

— Send another person to get medical aid.

Safety inspection guide

The intent of this inspection guide is to assist you in identifying potentially unsafe conditions on these products. Each machine, as it was designed and built, had required safety items installed to protect users and service personnel from injury. This guide addresses only those items. However, good judgment should be used to identify potential safety hazards due to attachment of non-IBM features or options not covered by this inspection guide.

If any unsafe conditions are present, you must determine how serious the apparent hazard could be and whether you can continue without first correcting the problem.

Consider these conditions and the safety hazards they present:

198


• Electrical hazards, especially primary power (primary voltage on the frame can cause serious or fatal electrical shock).

• Explosive hazards, such as a damaged CRT face or bulging capacitor

• Mechanical hazards, such as loose or missing hardware

The guide consists of a series of steps presented in a checklist. Begin the checks with the power off, and the power cord disconnected.

Checklist:

1. Check exterior covers for damage (loose, broken, or sharp edges).

2. Power-off the computer. Disconnect the power cord.

3. Check the power cord for: a. A third-wire ground connector in good condition.

Use a meter to measure third-wire ground continuity for 0.1 ohm or less between the external ground pin and frame ground.

b. The power cord should be the appropriate type as specified in the parts listings.

c. Insulation must not be frayed or worn.

4. Remove the cover.

5. Check for any obvious non-IBM alterations. Use good judgment as to the safety of any non-IBM alterations.

6. Check inside the unit for any obvious unsafe conditions, such as metal filings, contamination, water or other liquids, or signs of fire or smoke damage.

7. Check for worn, frayed, or pinched cables.

8. Check that the power-supply cover fasteners (screws or rivets) have not been removed or tampered with.

Handling electrostatic dischargesensitive devices

Any computer part containing transistors or integrated circuits (ICs) should be considered sensitive to electrostatic discharge (ESD). ESD damage can occur when there is a difference in charge between objects. Protect against ESD damage by equalizing the charge so that the machine, the part, the work mat, and the person handling the part are all at the same charge.

Notes:

1. Use product-specific ESD procedures when they exceed the requirements noted here.

2. Make sure that the ESD protective devices you use have been certified (ISO 9000) as fully effective.

When handling ESD-sensitive parts:

• Keep the parts in protective packages until they are inserted into the product.

• Avoid contact with other people.


199

• Wear a grounded wrist strap against your skin to eliminate static on your body.

• Prevent the part from touching your clothing. Most clothing is insulative and retains a charge even when you are wearing a wrist strap.

• Use the black side of a grounded work mat to provide a static-free work surface. The mat is especially useful when handling ESD-sensitive devices.

• Select a grounding system, such as those listed below, to provide protection that meets the specific service requirement.

Note: The use of a grounding system is desirable but not required to protect against ESD damage.

— Attach the ESD ground clip to any frame ground, ground braid, or green-wire ground.

— Use an ESD common ground or reference point when working on a double-insulated or batteryoperated system. You can use coax or connectoroutside shells on these systems.

— Use the round ground-prong of the ac plug on acoperated computers.

Grounding requirements

Electrical grounding of the computer is required for operator safety and correct system function. Proper grounding of the electrical outlet can be verified by a certified electrician.

Safety notices (multi-lingual translations)

The caution and danger safety notices in this section are provided in the following languages:

• English

• Brazilian/Portuguese

• Chinese

• French

• German

• Italian

• Korean

• Spanish

Important: All caution and danger statements in this

Netfinity Server Library

begin with a number. This number is used to cross reference an English caution or danger statement with translated versions of the caution or danger statement in this section.

For example, if a caution statement begins with a number 1, translations for that caution statement appear in this section under statement 1.

Be sure to read all caution and danger statements before performing any of the instructions.

200


• Statement 1

DANGER

Electrical current from power, telephone and communication cables is hazardous.

To avoid a shock hazard:

•

Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm.

•

Connect all power cords to a properly wired and grounded electrical outlet.

•

Connect to properly wired outlets any equipment that will be attached to this product.

•

When possible, use one hand only to connect or disconnect signal cables.

•

Never turn on any equipment when there is evidence of fire, water, or structural damage.

•

Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration proce-

dures.

•

Connect and disconnect cables as described in the following table when installing, moving, or opening covers on this product or attached devices.

To Connect


2. First, attach all cables to devices.

3. Attach signal cables to connectors.

4. Attach power cords to outlet.

5. Turn device ON.

To Disconnect


2. First, remove power cords from outlet.

3. Remove signal cables from connectors.

4. Remove all cables from devices.

• Statement 2


201

CAUTION:

When replacing the lithium battery, use only IBM Part

Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.

Do not:

• Throw or immerse into water

• Heat to more than 100

°

C (212

°

F)

• Repair or disassemble

Dispose of the battery as required by local ordinances or regulations.

• Statement 3

CAUTION:

When laser products (such as CD-ROMs, DVD-ROM drives, fiber optic devices, or transmitters) are installed, note the following:

• Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device.

• Use of controls or adjustments or performance of procedures other than those specified herein might result in hazardous radiation exposure.

DANGER

Some laser products contain an embedded Class 3A or

Class 3B laser diode. Note the following:

Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam.

• Statement 4

202


≥

18 kg (37 lbs)

≥

32 kg (70.5 lbs)

≥

55 kg (121.2 lbs)

CAUTION:

Use safe practices when lifting.

• Statement 5

CAUTION:

The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.

2

1

• Statement 10

CAUTION:

Do not place any object weighing more than 82 kg (180 lbs.) on top of rack-mounted devices.


203

Importante:

Todas as instruções de cuidado e perigo da

Netfinity Server

Library

começam com um número. Este número é utilizado para fazer referência cruzada de uma instrução de cuidado ou perigo no idioma inglês com as versões traduzidas das instruções de cuidado ou perigo encontradas nesta seção.

Por exemplo, se uma instrução de cuidado é iniciada com o número 1, as traduções para aquela instrução de cuidado aparecem nesta seção sob a instrução 1.

Certifique-se de ler todas as instruções de cuidado e perigo antes de executar qualquer operação.

Instrução 1

PERIGO

A corrente elétrica proveniente de cabos de alimentação, de telefone e de comunicações é perigosa.

Para evitar risco de choque:

• Não conecte ou desconecte cabos e não realize instalação, manutenção ou reconfiguração deste produto durante uma tempestade com raios.

• Conecte todos os cabos de alimentação a tomadas elétricas corretamente instaladas e aterradas.

• Conecte todos os equipamentos ao qual esse produto será conectado a tomadas corretamente instaladas.

• Sempre que possível, utilize apenas uma das mãos para conectar ou desconectar cabos de sinal.

• Nunca ligue qualquer equipamento quando existir evidência de danos por fogo, água ou na estrutura.

• Desconecte cabos de alimentação, sistemas de telecomunicação, redes e modems antes de abrir as tampas dos dispositivos, a menos que especificado de maneira diferente nos procedimentos de instalação e configuração.

• Conecte e desconecte cabos conforme descrito na seguinte tabela, ao instalar ou movimentar este produto ou os dispositivos conectados, ou ao abrir suas tampas.

204


Para Conectar:

1. DESLIGUE Tudo.

2. Primeiramente, conecte todos os cabos aos dispositivos.

3. Conecte os cabos de sinal aos conectores.

4. Conecte os cabos de alimentação às tomadas.

5. LIGUE os dispositivos.

Para Desconectar:

1. DESLIGUE Tudo.

2. Primeiramente, remova os cabos de alimentação das tomadas.

3. Remova os cabos de sinal dos conectores.

4. Remova todos os cabos dos dispositivos.

Instrução 2

CUIDADO:

Ao substituir a bateria de lítio, utilize apenas uma bateria

IBM, Número de Peça 33F8354 ou uma bateria de tipo equivalente, recomendada pelo fabricante. Se o seu sistema possui um móídulo com uma bateria de lítio, substitua-o apenas pelo mesmo tipo de mídulo, do mesmo fabricante. A bateria contém lítio e pode explodir se não for utilizada, manuseada e descartada de maneira correta.

Não:

• Jogue ou coloque na água

• Aqueça a mais de 100°C (212°F)

• Conserte nem desmonte

Para descartar a bateria, entre em contato com a área de atendimento a clientes IBM, pelo telefone (011) 889-8986, para obter informações sobre como enviar a bateria pelo correio para a IBM.

Instrução 3

PRECAUCIÓN:

Quando produtos a laser (unidades de CD-ROM, unidades de DVD, dispositivos de fibra ítica, transmissores, etc.) estiverem instalados, observe o seguinte:


205

• Não remova as tampas. A remoção das tampas de um produto a laser pode resultar em exposição prejudicial

à radiação de laser. Nenhuma peça localizada no interior do dispositivo pode ser consertada.

• A utilização de controles ou ajustes ou a execução de procedimentos diferentes dos especificados aqui pode resultar em exposição prejudicial à radiação.

PERIGO

Alguns produtos a laser contêm um diodo laser da Classe

3A ou Classe 3B embutido. Observe o seguinte:

Radiação de laser quando aberto. Não olhe diretamente para o raio a olho nu ou com instrumentos íticos, e evite exposição direta ao raio.

Instrução 4

≥

18 kg (37 lbs)

CUIDADO:

Ao levantar a máquina, faça-o com segurança.

Instrução 5

≥

32 kg (70,5 lbs)

≥

55 kg (121,2 lbs)

CUIDADO:

Os botões Liga/Desliga localizados no dispositivo e na fonte de alimentação não desligam a corrente elétrica fornecida ao dispositivo. O dispositivo também pode ter mais de um

206


cabo de alimentação. Para remover toda a corrente elétrica do dispositivo, assegure que todos os cabos de alimentação estejam desconectados da fonte de energia elétrica.

2

1

CUIDADO:

Instrução 10

CUIDADO:

Não coloque nenhum objeto com peso superior a 82 kg (180 lbs.) sobre dispositivos montados em rack.


207

208



209

210



211

212



213

214



215

Important:

Toutes les consignes Attention et Danger indiquées dans la bibliothèque

Netfinity Server

sont précédées d'un numéro.

Ce dernier permet de mettre en correspondance la consigne en anglais avec ses versions traduites dans la présente section.

Par exemple, si une consigne de type Attention est précédée du chiffre 1, ses traductions sont également précédées du chiffre 1 dans la présente section.

Prenez connaissance de toutes les consignes de type Attention et Danger avant de procéder aux opérations décrites par les instructions.

Notice n° 1

DANGER

Le courant électrique passant dans les câbles de communication, ou les cordons téléphoniques et d'alimentation peut

être dangereux.

Pour éviter tout risque de choc électrique:

• Ne manipulez aucun câble et n'effectuez aucune opération d'installation, d'entretien ou de reconfiguration de ce produit au cours d'un orage.

• Branchez tous les cordons d'alimentation sur un socle de prise de courant correctement câblé et mis à la terre.

• Branchez sur des socles de prise de courant correctement câblés tout équipement connecté à ce produit.

• Lorsque cela est possible, n'utilisez qu'une seule main pour connecter ou déconnecter les câbles d'interface.

• Ne mettez jamais un équipement sous tension en cas d'incendie ou d'inondation, ou en présence de dommages matériels.

• Avant de retirer les carters de l'unité, mettez celle-ci hors tension et déconnectez ses cordons d'alimentation, ainsi que les câbles qui la relient aux réseaux, aux systèmes de télécommunication et aux modems (sauf instruction contraire mentionnée dans les procédures d'installation et de configuration).

• Lorsque vous installez ou que vous déplacez le présent produit ou des périphériques qui lui sont raccordés, reportez-vous aux instructions ci-dessous pour connecter et déconnecter les différents cordons.

216


Connexion

1. Mettez les unités hors tension.

2. Commencez par brancher tous les cordons sur les unités.

3. Branchez les câbles d'interface sur des connecteurs.

4. Branchez les cordons d'alimentation sur des prises.

5. Mettez les unités sous tension.

Déconnexion

1. Mettez les unités hors tension.

2. Débranchez les cordons d'alimentation des prises.

3. Débranchez les câbles d'interface des connecteurs.

4. Débranchez tous les câbles des unités.

Notice n° 2

ATTENTION:

Remplacez la pile au lithium usagée par une pile de référence identique exclusivement - voir la référence

IBM - ou par une pile équivalente recommandée par le fabricant. Si votre système est doté d'un module contenant une pile au lithium, vous devez le remplacer uniquement par un module identique, produit par le même fabricant. La pile contient du lithium et présente donc un risque d'explosion en cas de mauvaise manipulation ou utilisation.

•

Ne la jetez pas à l'eau.

•

Ne l'exposez pas à une température supérieure à

100

°

C.

•

Ne cherchez pas à la réparer ou à la démonter.

Pour la mise au rebut, reportez-vous à la réglementation en vigueur.

Notice n° 3

ATTENTION:

Si des produits laser sont installés (tels que des unités de CD-ROM ou de DVD, des périphériques contenant


217

des fibres optiques ou des émetteurs-récepteurs), prenez connaissance des informations suivantes:

•

N'ouvrez pas ces produits pour éviter une exposition directe au rayon laser. Vous ne pouvez effectuer aucune opération de maintenance à l'intérieur.

•

Pour éviter tout risque d'exposition au rayon laser, respectez les consignes de réglage et d'utilisation des commandes, ainsi que les procédures décrites dans le présent document.

DANGER

Certains produits laser contiennent une diode laser de classe 3A ou 3B. Prenez connaissance des informations suivantes:

Rayonnement laser lorsque le carter est ouvert. évitez de regarder fixement le faisceau ou de l'observer à l'aide d'instruments optiques. évitez une exposition directe au rayon.

Notice n° 4

≥

18 kg

ATTENTION:

≥

32 kg

Faites-vous aider pour soulever ce produit.

Notice n° 5

≥

55 kg

ATTENTION:

218


Le bouton de mise sous tension/hors tension de l'unité et l'interrupteur d'alimentation du bloc d'alimentation ne coupent pas l'arrivée de courant électrique à l'intérieur de la machine. Il se peut que votre unité dispose de plusieurs cordons d'alimentation. Pour isoler totalement l'unité du réseau électrique, débranchez tous les cordons d'alimentation des socles de prise de courant.

2

1

Notice n° 10

ATTENTION:

Ne posez pas d'objet dont le poids dépasse 82 kg sur les unités montées en armoire.


219

Wichtig:

Alle Sicherheitshinweise in dieser

Netfinity Server-Bibliothek

beginnen mit einer Nummer. Diese Nummer verweist auf einen englischen Sicherheitshinweis mit den übersetzten

Versionen dieses Hinweises in diesem Abschnitt.

Wenn z. B. ein Sicherheitshinweis mit der Nummer 1 beginnt, so erscheint die übersetzung für diesen Sicherheitshinweis in diesem Abschnitt unter dem Hinweis 1.

Lesen Sie alle Sicherheitshinweise, bevor Sie eine

Anweisung ausführen.

Hinweis 1

VORSICHT

Elektrische Spannungen von Netz-, Telefon- und Datenübertragungsleitungen sind gefährlich.

Aus Sicherheitsgründen:

• Bei Gewitter an diesem Gerät keine Kabel anschließen oder lösen. Ferner keine Installations-, Wartungs- oder

Rekonfigurationsarbeiten durchführen.

• Gerät nur an eine Schutzkontaktsteckdose mit ordnungsgemäß geerdetem Schutzkontakt anschließen.

• Alle angeschlossenen Geräte ebenfalls an Schutzkontaktsteckdosen mit ordnungsgemäß geerdetem

Schutzkontakt anschließen.

• Signalkabel möglichst einhändig anschließen oder lösen.

• Keine Geräte einschalten, wenn die Gefahr einer Beschädigung durch Feuer, Wasser oder andere Einflüsse besteht.

• Die Verbindung zu den angeschlossenen Netzkabeln,

Telekommunikationssystemen, Netzwerken und

Modems ist vor dem öffnen des Gehäuses zu unterbrechen. Es sei denn, dies ist in den zugehörigen Installations- und Konfigurationsprozeduren anders angegeben.

• Nur nach den nachfolgend aufgeführten Anweisungen arbeiten, die für Installation, Transport oder öffnen von

Gehäusen von Personal Computern oder angeschlossenen Einheiten gelten.

220


Kabel anschlie

β

en:

1. Alle Geräte ausschalten und

Netzstecker ziehen.

2. Zuerst alle Kabel an

Einheiten anschließen.

3. Signalkabel an

Anschlußbuchsen anschließen.

4. Netzstecker an

Steckdose anschließen.

5. Gerät einschalten.

Hinweis 2

Kabel lösen:

1. Alle Geräte ausschalten.

2. Zuerst Netzstecker von

Steckdose lösen.

3. Signalkabel von

Anschlußbuchsen lösen.

4. Alle Kabel von

Einheiten lösen.

ACHTUNG:

Eine verbrauchte Batterie nur durch eine Batterie mit der

IBM Teilenummer 33F8354 oder durch eine vom Hersteller empfohlene Batterie ersetzen. Wenn Ihr System ein Modul mit einer Lithium-Batterie enthält, ersetzen Sie es immer mit dem selben Modultyp vom selben Hersteller. Die Batterie enthält Lithium und kann bei unsachgemäßer Verwendung,

Handhabung oder Entsorgung explodieren.

Die Batterie nicht:

• mit Wasser in Berührung bringen.

• über 100 C erhitzen.

• reparieren oder zerlegen.

Die örtlichen Bestimmungen für die Entsorgung von Sondermüll beachten.

Hinweis 3

ACHTUNG:

Wenn ein Laserprodukt (z. B. CD-ROM-Laufwerke, DVD-

Laufwerke, Einheiten mit Glasfaserkabeln oder Transmitter) installiert ist, beachten Sie folgendes.


221

• Das Entfernen der Abdeckungen des CD-ROM-Laufwerks kann zu gefährlicher Laserstrahlung führen. Es befinden sich keine Teile innerhalb des CD-ROM-Laufwerks, die vom Benutzer gewartet werden müssen. Die

Verkleidung des CD-ROM-Laufwerks nicht öffnen.

• Steuer- und Einstellelemente sowie Verfahren nur entsprechend den Anweisungen im vorliegenden

Handbuch einsetzen. Andernfalls kann gefährliche

Laserstrahlung auftreten.

VORSICHT

Manche CD-ROM-Laufwerke enthalten eine eingebaute

Laserdiode der Klasse 3A oder 3B. Die nachfolgend aufgeführten Punkte beachten.

Laserstrahlung bei geöffneter Tür. Niemals direkt in den

Laserstrahl sehen, nicht direkt mit optischen Instrumenten betrachten und den Strahlungsbereich meiden.

Hinweis 4

≥

18 kg

ACHTUNG:

≥

32 kg

≥

55 kg

Beim Anheben der Maschine die vorgeschriebenen Sicherheitsbestimmungen beachten.

Hinweis 5

ACHTUNG:

222


Mit dem Betriebsspannungsschalter an der Vorderseite des

Servers und dem Betriebsspannungsschalter am Netzteil wird die Stromversorgung für den Server nicht unterbrochen. Der Server könnte auch mehr als ein Netzkabel aufweisen. Um die gesamte Stromversorgung des Servers auszuschalten, muß sichergestellt werden, daß alle Netzkabel aus den Netzsteckdosen herausgezogen wurden.

2

1

Hinweis 10

ACHTUNG:

Keine Gegenstände, die mehr als 82 kg wiegen, auf Rack-

Einheiten ablegen.


223

Importante:

Tutti gli avvisi di attenzione e di pericolo riportati nella pubblicazione

Netfinity Server Library

iniziano con un numero.

Questo numero viene utilizzato per confrontare avvisi di attenzione o di pericolo in inglese con le versioni tradotte riportate in questa sezione.

Ad esempio, se un avviso di attenzione inizia con il numero

1, la relativa versione tradotta è presente in questa sezione con la stessa numerazione.

Prima di eseguire una qualsiasi istruzione, accertarsi di leggere tutti gli avvisi di attenzione e di pericolo.

Avviso 1

PERICOLO

La corrente elettrica circolante nei cavi di alimentazione, del telefono e di segnale è pericolosa.

Per evitare il pericolo di scosse elettriche:

• Non collegare o scollegare i cavi, non effettuare l'installazione, la manutenzione o la riconfigurazione di questo prodotto durante i temporali.

• Collegare tutti i cavi di alimentazione ad una presa elettrica correttamente cablata e munita di terra di sicurezza.

• Collegare qualsiasi apparecchiatura collegata a questo prodotto ad una presa elettrica correttamente cablata e munita di terra di sicurezza.

• Quando possibile, collegare o scollegare i cavi di segnale con una sola mano.

• Non accendere qualsiasi apparecchiatura in presenza di fuoco, acqua o se sono presenti danni all'apparecchiatura stessa.

• Scollegare i cavi di alimentazione, i sistemi di telecomunicazioni, le reti e i modem prima di aprire i coperchi delle unità, se non diversamente indicato nelle procedure di installazione e configurazione.

• Collegare e scollegare i cavi come descritto nella seguente tabella quando si effettuano l'installazione, la rimozione o l'apertura dei coperchi di questo prodotto o delle unità collegate.

224


Per collegare:

1. SPEGNERE tutti i dispositivi.

2. Collegare prima tutti i cavi alle unità.

3. Collegare i cavi di segnale ai connettori.

4. Collegare i cavi di alimentazione alle prese elettriche.

5. ACCENDERE le unità.

Per scollegare:

1. SPEGNERE tutti i dispositivi.

2. Rimuovere prima i cavi di alimentazione dalle prese elettriche.

3. Rimuovere i cavi di segnale dai connettori.

4. Rimuovere tutti i cavi dalle unità.

Avviso 2

ATTENZIONE:

Quando si sostituisce la batteria al litio, utilizzare solo una batteria IBM con numero parte 33F8354 o batterie dello stesso tipo o di tipo equivalente consigliate dal produttore.

Se il sistema di cui si dispone è provvisto di un modulo contenente una batteria al litio, sostituire tale batteria solo con un tipo di modulo uguale a quello fornito dal produttore. La batteria contiene litio e può esplodere se utilizzata, maneggiata o smaltita impropriamente.

Evitare di:

• Gettarla o immergerla in acqua

• Riscaldarla ad una temperatura superiore ai 100°C

• Cercare di ripararla o smontarla

Smaltire secondo la normativa in vigore (D.Lgs 22 del 5/2/9) e successive disposizioni nazionali e locali.

Avviso 3

ATTENZIONE:

Quando si installano prodotti laser come, ad esempio, le unità DVD, CD-ROM, a fibre ottiche o trasmettitori, prestare attenzione a quanto segue:

• Non rimuovere i coperchi. L'apertura dei coperchi di prodotti laser può determinare l'esposizione a radiazi-


225

oni laser pericolose. All'interno delle unità non vi sono parti su cui effettuare l'assistenza tecnica.

• L'utilizzo di controlli, regolazioni o l'esecuzione di procedure non descritti nel presente manuale possono provocare l'esposizione a radiazioni pericolose.

PERICOLO

Alcuni prodotti laser contengono all'interno un diodo laser di

Classe 3A o Classe 3B. Prestare attenzione a quanto segue:

Aprendo l'unità vengono emesse radiazioni laser. Non fissare il fascio, non guardarlo direttamente con strumenti ottici ed evitare l'esposizione diretta al fascio.

Avviso 4

≥

18 kg

ATTENZIONE:

≥

32 kg

≥

55 kg

Durante il sollevamento della macchina seguire delle norme di sicurezza.

Avviso 5

ATTENZIONE:

Il pulsante del controllo dell'alimentazione situato sull'unità e l'interruttore di alimentazione posto sull'alimentatore non disattiva la corrente elettrica fornita all'unità. L'unità potrebbe

226


disporre di più di un cavo di alimentazione. Per disattivare la corrente elettrica dall'unità, accertarsi che tutti i cavi di alimentazione siano scollegati dalla sorgente di alimentazione.

2

1

Avviso 10

ATTENZIONE:

Non poggiare oggetti che pesano più di 82 kg sulla parte superiore delle unità montate in rack.


227

228



229

230


Importante:

Todas las declaraciones de precauciín de esta

Biblioteca del servidor Netfinity

empiezan con un número. Dicho número se emplea para establecer una referencia cruzada de una declaraciín de precauciín o peligro en inglés con las versiones traducidas que de dichas declaraciones pueden encontrarse en esta secciín.

Por ejemplo, si una declaraciín de peligro empieza con el número 1, las traducciones de esta declaraciín de precauciín aparecen en esta secciín bajo Declaraciín 1.

Lea atentamente todas las declaraciones de precauciín y peligro antes de llevar a cabo cualquier operaciín.

Declaración 1

PELIGRO

La corriente eléctrica de los cables telefínicos, de alimentaciín y de comunicaciones es perjudicial.

Para evitar una descarga eléctrica:

• No conecte ni desconecte ningún cable ni realice las operaciones de instalaciín, mantenimiento o reconfiguraciín de este producto durante una tormenta.

• Conecte cada cable de alimentaciín a una toma de alimentaciín eléctrica con conexiín a tierra y cableado correctos.

• Conecte a tomas de alimentaciín con un cableado correcto cualquier equipo que vaya a estar conectado a este producto.

• Si es posible, utilice una sola mano cuando conecte o desconecte los cables de sent.al.

• No encienda nunca un equipo cuando haya riesgos de incendio, de inundaciín o de daños estructurales.

• Desconecte los cables de alimentaciín, sistemas de telecomunicaciones, redes y mídems conectados antes de abrir las cubiertas del dispositivo a menos que se indique lo contrario en los procedimientos de instalaciín y configuraciín.

• Conecte y desconecte los cables tal como se describe en la tabla siguiente cuando desee realizar una operaciín de instalaciín, de traslado o de apertura de las cubiertas para este producto o para los dispositivos conectados.


231

Para la conexin

1. APÁGUELO todo.

2. En primer lugar, conecte los cables a los dispositivos.

3. Conecte los cables de señal a los conectores.

4. Conecte cada cable de alimentaciín a la toma de alimentaciín.

5. ENCIENDA el dispositivo.

Para la desconexiín

1. APÁGUELO todo.

2. En primer lugar, retire cada cable de alimentaciín de la toma de alimentaciín.

3. Retire los cables de señal de los conectores.

4. Retire los cables de los dispositivos.

Declaración 2

PRECAUCIÓN:

Cuando desee sustituir la batería de litio, utilice únicamente el número de pieza 33F8354 de IBM o cualquier tipo de batería equivalente que recomiende el fabricante. Si el sistema tiene un mídulo que contiene una batería de litio, sustitúyalo

únicamente por el mismo tipo de mídulo, que ha de estar creado por el mismo fabricante. La batería contiene litio y puede explotar si el usuario no la utiliza ni la maneja de forma adecuada o si no se desprende de la misma como corresponde.

No realice las acciones siguientes:

• Arrojarla al agua o sumergirla

• Calentarla a una temperatura que supere los 100°C

(212°F)

• Repararla o desmontarla

Despréndase de la batería siguiendo los requisitos que exija el reglamento o la legislaciín local.

Declaración 3

PRECAUCIÓN:

Cuando instale productos láser (como, por ejemplo, CD-

ROM, unidades DVD, dispositivos de fibra íptica o transmisores), tenga en cuenta las advertencias siguientes:

232


• No retire las cubiertas. Si retira las cubiertas del producto láser, puede quedar expuesto a radiaciín láser perjudicial. Dentro del dispositivo no existe ninguna pieza que requiera mantenimiento.

• El uso de controles o ajustes o la realizaciín de procedimientos que no sean los que se han especificado aquí pueden dar como resultado una exposiciín perjudicial a las radiaciones.

PELIGRO

Algunos productos láser contienen un diodo de láser incorporado de Clase 3A o de Clase 3B. Tenga en cuenta la advertencia siguiente.

Cuando se abre, hay radiaciín láser. No mire fijamente el rayo ni lleve a cabo ningún examen directamente con instrumentos ípticos; evite la exposiciín directa al rayo.

Declaración 4

≥

18 kg (37 libras)

≥

32 kg (70,5 libras)

≥

55 kg (121,2 libras)

PRECAUCIÓN:

Tome medidas de seguridad al levantar el producto.

Declaración 5

PRECAUCIÓN:


233

El botín de control de alimentaciín del dispositivo y el interruptor de alimentaciín de la fuente de alimentaciín no apagan la corriente eléctrica suministrada al dispositivo. Es posible también que el dispositivo tenga más de un cable de alimentaciín. Para eliminar la corriente eléctrica del dispositivo, asegúrese de desconectar todos los cables de alimentaciín de la fuente de alimentaciín.

2

1

Declaración 10

PRECAUCIÓN:

No coloque ningún objeto que pese más de 82 kg (180 libras) encima de los dispositivos montados en bastidor.

234


Send us your comments!

We want to know your opinion about this manual (part number 19K2479). Your input will help us to improve our publications.

Please photocopy this survey, complete it, and then fax it to

IBM HMM Survey at 919-543-8167 (USA).

Name: _________________________________________

Phone number: __________________________________

1.

Do you like this manual?

❑

Yes

❑

No

_________________________________________

_________________________________________

2.

What would you like to see added, changed, or deleted in this manual?

_________________________________________

_________________________________________

3.

What is your service experience level?

❑

Less than five years

❑

More than five years

4.

Which Servers to you service most?

_________________________________________

_________________________________________

_________________________________________

_________________________________________

Thank you for your response!


235

Problem determination tips

Due to the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions.

• Machine type and model

• Processor or hard disk upgrades

• Failure symptom

— Do diagnostics fail?

— What, when, where, single, or multiple systems?

— Is the failure repeatable?

— Has this configuration ever worked?

— If it has been working, what changes were made prior to it failing?

— Is this the original reported failure?

• Reference/Diagnostics version

— Type and version level

• Hardware configuration

— Print (print screen) configuration currently in use

— BIOS level

• Operating system software

— Type and version level

Note: To eliminate confusion, identical systems are considered identical only if they:

1. Are the exact machine type and models

2. Have the same BIOS level

3. Have the same adapters/attachments in the same locations

4. Have the same address jumpers/terminators/cabling

5. Have the same software versions and levels

6. Have the same Reference/Diagnostics Diskette

(version)

7. Have the same configuration options set in the system

8. Have the same setup for the operation system control files

Comparing the configuration and software set-up between "working and non-working" systems will often lead to problem resolution.

Notices

References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Subject to IBM’s valid intellectual property or other

236


legally protectable rights, any functionally equivalent product, program, or service may be used instead of the IBM product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, are the responsibility of the user.

Trademarks

The following items are trademarks of the IBM Corporation in the United States or other countries or both:

HelpCenter

IBM

NetBAY3

Netfinity Manager

SystemXtra

HelpFax

OS/2

Netfinity

ThinkPad

The following terms are trademarks of other companies:

Notes Lotus Development Corporation

MMX and Pentium are trademarks or registered trademarks of Intel Corporation.

UNIX is a trademark or registered trademark of The Open

Group in the United States and other countries.

Windows NT is a trademark or registered trademark of

Microsoft Corporation.


237

238


IBM

Part Number: 19K2479

File Number:

Printed in the United States of America on recycled paper containing 10& recovered post-consumer fiber.

IBM Netfinity 6000R Hardware Maintenance Manual

Assistant Bot

IBM Netfinity Servers

IBM Netfinity 6000R - Type 8682

Models 1RY, 2RY

Hardware Maintenance Manual

March 2000

IBM Netfinity Servers

IBM Netfinity 6000R - Type 8682

Models 1RY, 2RY

Hardware Maintenance Manual

March 2000

About this manual

Important safety information

Online support

IBM online addresses

Contents

General checkout

General information

Features and specifications

Server features

hot-swap

hot-plug

hot-add

Reliability, availability, and serviceability

Start the server

Controls and indicators

Information LED panel

Diagnostics

Diagnostic tools overview

path of lights

POST

POST beep codes

POST error messages

Event/error logs

Small computer system interface messages

ServerGuide error symptoms

Netfinity Setup and

Installation CD

Operating

System Installation

your

Netfinity Setup and Installation

Diagnostic programs and error messages

first

Text messages

Starting the diagnostic programs

Viewing the test log

Diagnostic error message tables

Light path diagnostics

path

Power supply LEDs

Diagnostic panel LEDs

Light path diagnostics

Table 1. Light path diagnostics

Table 1. Light path diagnostics

Power checkout

Recovering BIOS

Replacing the battery

Do not:

Temperature checkout

Diagnosing errors

Troubleshooting the Ethernet controller

Network connection problems

X

Ethernet controller troubleshooting chart

Table 2. Ethernet troubleshooting chart

X

Table 2. Ethernet troubleshooting chart

Ethernet controller messages

Novell NetWare or IntraNetWare server ODI driver messages

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

Table 3. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller

Network driver interface specification 2.01

(OS/2) driver messages

Table 4. NDIS 2.01 (OS/2) driver messages for the Ethernet controller

Table 4. NDIS 2.01 (OS/2) driver messages for the Ethernet controller