IBM Netfinity 4500R Type 8656, 8656 Hardware Maintenance Manual

Hardware Maintenance Manual

Netfinity 4500R Type 8656

IBM

Hardware Maintenance Manual

Netfinity 4500R Type 8656

IBM

Note:

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

First Edition (April 2000) The following paragraph does not apply to the United Kingdom or any country where such provisions are

inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time.

This publication was developed for products and services offered in the United States of America. IBM may not offer the products, services, or features discussed in this document in other countries, and the information is subject 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.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

About this manual

This manual contains diagnostic information, a Symptom-to-FRU index, service information, error codes, error messages, and configuration information for the Netfinity 4500R (Type 8656, Models 1RY, 2RY).

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.

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

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

Online support

Use the World Wide Web (WWW) to download Diagnostic, BIOS Flash, and Device Driver files, and documents.

The web address is:

http://www.ibm.com/pc/support

iv Hardware Maintenance Manual: Netfinity 4500R Type 8656

Contents

About this manual . . . . . . . . . . . . . . . . . . . iii

Important safety information . . . . . . . . . . . . . . . . . . . . . . iii

Online support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

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

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

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

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

Reliability, availability, and serviceability features . . . . 6

Controls and indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Operator information panel. . . . . . . . . . . . . . . . . . . . . . . . 9

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . 11

Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . . . . . 11

Identifying problems using LEDs. . . . . . . . . . . . . . . . . . 11

Power supply LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Light path diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . 11

Diagnostics panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Light path diagnostics table . . . . . . . . . . . . . . . . . . . . 12

POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

POST error messages. . . . . . . . . . . . . . . . . . . . . . . . . . 13

Event/error logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Small computer system interface messages . . . . . . . . . 13

Diagnostic programs and error messages . . . . . . . . . . . 13

Text messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Starting the diagnostic programs . . . . . . . . . . . . . . . 14

Viewing the test log . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Diagnostic error message tables . . . . . . . . . . . . . . . . 15

Recovering BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Troubleshooting the Ethernet controller . . . . . . . . . . . . 16

Network connection problems. . . . . . . . . . . . . . . . . . 16

Ethernet controller troubleshooting chart . . . . . . . . 17

Ethernet controller messages. . . . . . . . . . . . . . . . . . . . . . 19

Novell NetWare or IntraNetWare server ODI driver

messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Network driver interface specification 2.01 (OS/2)

driver messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

NDIS 4.0 (Windows NT) driver messages . . . . . . . . 23

UNIX messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Power checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Replacing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

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

Configuring the server . . . . . . . . . . . . . . . 29

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

Starting the Configuration/Setup Utility program 29

Choices available from the Configuration/Setup main

menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Using passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Power-on password . . . . . . . . . . . . . . . . . . . . . . . . 34

Administrator password . . . . . . . . . . . . . . . . . . . . 35

Using the SCSISelect utility program. . . . . . . . . . . . . . . 36

Starting the SCSISelect utility program . . . . . . . . . . 36

Choices available from the SCSISelect menu . . . . . 37

Installing options . . . . . . . . . . . . . . . . . . . 39

Exploded view of the Netfinity 4500R . . . . . . . . . . . . . . 39

System board layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

System board options connectors . . . . . . . . . . . . . . . 40

System board internal cable connectors . . . . . . . . . . 41

System board external port connectors . . . . . . . . . . 41

System board switches and jumpers. . . . . . . . . . . . . 42

System board LED locations. . . . . . . . . . . . . . . . . . . . 44

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

System reliability considerations. . . . . . . . . . . . . . . . 46

Working inside a server with power on . . . . . . . . . . 46

Handling static-sensitive devices. . . . . . . . . . . . . . . . 46

Removing the cover and bezel. . . . . . . . . . . . . . . . . . . . . 47

Working with adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Adapter considerations . . . . . . . . . . . . . . . . . . . . . . . . 48

Adapter installation instructions. . . . . . . . . . . . . . . . . . . 49

Installing internal drives. . . . . . . . . . . . . . . . . . . . . . . . . . 50

Internal drive bays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

SCSI drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

SCSI IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Installing a hot-swap drive . . . . . . . . . . . . . . . . . . . . . . . 52

Installing a non-hot-swap drive . . . . . . . . . . . . . . . . . . . 53

Installing a microprocessor . . . . . . . . . . . . . . . . . . . . . . . 55

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

Replacing a hot-swap fan assembly . . . . . . . . . . . . . . . . 59

Installing the server cover and bezel . . . . . . . . . . . . . . . 60

Connecting external options . . . . . . . . . . . . . . . . . . . . . . 60

Cabling requirements . . . . . . . . . . . . . . . . . . . . . . . . . 60

Setting SCSI IDs for external devices . . . . . . . . . . . . 61

Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . 61

Input/Output ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Parallel port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Viewing or changing the parallel-port assignments 62

Parallel port connector . . . . . . . . . . . . . . . . . . . . . . 62

Video port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Keyboard port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

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

Ultra3 SCSI ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SCSI cabling requirements. . . . . . . . . . . . . . . . . . . 65

Setting SCSI IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SCSI connector pin-number assignments . . . . . . 66

Serial ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Viewing or changing the serial-port assignments 67

Serial-port connectors. . . . . . . . . . . . . . . . . . . . . . . 67

Universal Serial Bus ports. . . . . . . . . . . . . . . . . . . . . . 68

USB cables and hubs. . . . . . . . . . . . . . . . . . . . . . . . 68

USB-port connectors. . . . . . . . . . . . . . . . . . . . . . . . 68

Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring the Ethernet controller. . . . . . . . . . . 69

Failover for redundant Ethernet. . . . . . . . . . . . . . 69

Ethernet port connector . . . . . . . . . . . . . . . . . . . . . 73

Advanced System Management ports . . . . . . . . . . . 73

Cabling the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Netfinity Manager . . . . . . . . . . . . . . . . . . . 75

Managing your IBM Netfinity server with Netfinity

Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Netfinity Manager documentation . . . . . . . . . . . . . . . . . 75

Netfinity Manager system requirements . . . . . . . . . . . . 76

Netfinity Manager for OS/2 system requirements . 76 Netfinity Manager for Windows 95 and Windows 98

system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Netfinity Manager for Windows NT system

requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Starting the Netfinity Manager installation program . 78

Netfinity Manager database support . . . . . . . . . . . . . . . 83

DB2 database support . . . . . . . . . . . . . . . . . . . . . . . . . 83

System requirements . . . . . . . . . . . . . . . . . . . . . . . 83

Installing and configuring the database . . . . . . . 84

Activating the database . . . . . . . . . . . . . . . . . . . . . 84

Granting and revoking database privileges . . . . 85

Deleting the database. . . . . . . . . . . . . . . . . . . . . . . 87

Lotus Notes database support . . . . . . . . . . . . . . . . . . 87

System requirements . . . . . . . . . . . . . . . . . . . . . . . 87

Installing the database . . . . . . . . . . . . . . . . . . . . . . 88

Browsing the Netfinity Manager Lotus Notes

database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

ODBC database support. . . . . . . . . . . . . . . . . . . . . . . 89

System requirements . . . . . . . . . . . . . . . . . . . . . . . 89

ODBC database configuration . . . . . . . . . . . . . . . 90

Creating the Netfinity Manager tables . . . . . . . . 90

Supported and certified databases. . . . . . . . . . . . 91

Starting Netfinity Manager . . . . . . . . . . . . . . . . . . . . . . . 92

Netfinity Manager Service Manager. . . . . . . . . . . . . 93

Netfinity Manager service descriptions . . . . . . . . . . 93

Advanced System Management. . . . . . . . . . . . . . 93

Alert Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Alert on LAN configuration . . . . . . . . . . . . . . . . . 94

Capacity Management . . . . . . . . . . . . . . . . . . . . . . 94

Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Critical File Monitor . . . . . . . . . . . . . . . . . . . . . . . . 94

DMI Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

ECC Memory Setup . . . . . . . . . . . . . . . . . . . . . . . . 95

Event Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

File Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Power-On Error Detect . . . . . . . . . . . . . . . . . . . . . 95

Predictive Failure Analysis . . . . . . . . . . . . . . . . . . 95

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

RAID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Remote Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Remote System Manager. . . . . . . . . . . . . . . . . . . . 96

Remote Workstation Control . . . . . . . . . . . . . . . . 96

Screen View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Security Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Serial Connection Control . . . . . . . . . . . . . . . . . . . 96

Service Configuration Manager . . . . . . . . . . . . . . 96

Software Inventory. . . . . . . . . . . . . . . . . . . . . . . . . 96

System Diagnostics Manager . . . . . . . . . . . . . . . . 97

System Information Tool . . . . . . . . . . . . . . . . . . . . 97

System Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

System Partition Access. . . . . . . . . . . . . . . . . . . . . 97

System Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Update Connector Manager . . . . . . . . . . . . . . . . . 97

Web Manager Configuration . . . . . . . . . . . . . . . . 98

Delaying Netfinity Manager startup on OS/2 systems 98 Getting more information about Netfinity Manager . . 98

Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Automated installation . . . . . . . . . . . . . . . . . . . . . . . . 99

Customized installation . . . . . . . . . . . . . . . . . . . . . . 100

FRU information (service only) . . . . . . . 103

Removing the LED cover . . . . . . . . . . . . . . . . . . . . . . . . 103

Removing the on/off reset board . . . . . . . . . . . . . . . . . 104

Removing the diskette/CDROM drive . . . . . . . . . . . . 104

Removing the LED board. . . . . . . . . . . . . . . . . . . . . . . . 105

Removing the SCSI backplane assembly . . . . . . . . . . . 105

Removing the hot-swap hard disk drive backplane . 106

Removing the power supply backplane. . . . . . . . . . . . 107

Removing the AC Distribution Box . . . . . . . . . . . . . . . 108

Removing the system board. . . . . . . . . . . . . . . . . . . . . . 109

Symptom-to-FRU index . . . . . . . . . . . . . 111

Beep symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

No Beep symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Information panel system error LED . . . . . . . . . . . . . . 114

Diagnostic error codes . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Power supply LED errors. . . . . . . . . . . . . . . . . . . . . . . . 121

POST error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

SCSI error codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Temperature error messages . . . . . . . . . . . . . . . . . . . . . 128

Fan error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Power error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Voltage related system shutdown . . . . . . . . . . . . . . 131

Temperature related system shutdown. . . . . . . . . . 131

DASD checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Host Built-In Self Test (BIST) . . . . . . . . . . . . . . . . . . . . . 132

Bus fault messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Undetermined problems . . . . . . . . . . . . . . . . . . . . . . . . 133

Parts listing (Type 8656). . . . . . . . . . . . . 135

Keyboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Power cords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Related service information. . . . . . . . . . 141

Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

General safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Electrical safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Safety inspection guide . . . . . . . . . . . . . . . . . . . . . . . 143

Handling electrostatic discharge-sensitive devices 144

Grounding requirements. . . . . . . . . . . . . . . . . . . . . . 145

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

Send us your comments! . . . . . . . . . . . . . . . . . . . . . . . . 180

Problem determination tips . . . . . . . . . . . . . . . . . . . . . . 181

Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

vi Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly.

When you run the diagnostic programs, a single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test.

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 “POST error codes” on page 122.

4. If the computer hangs and no error is displayed, go to “Undetermined problems” on page 133.

5. Power supply problems, see “Power supply LED errors” on page 121.

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

7. For intermittent problems, check the error log; see “Event/error logs” on page 13.

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. IS THE SYSTEM 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 122.

• Check the information LED panel System Error LED; if on, see “Information panel system error LED” on page 114.

• Check the System Error Log. If an error was recorded by the system, see“Symptom-to-FRU index” on page 111.

• Start the Diagnostic Programs. See “Starting the diagnostic programs” on page 14.

• 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 111. YES. Run the Diagnostic Programs. If necessary, refer to “Starting the diagnostic

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

If the diagnostics completed successfully and you still suspect a problem, see “Undetermined problems” on page 133.

2 Hardware Maintenance Manual: Netfinity 4500R Type 8656

General information

Your Netfinity 4500R server is a high-performance server that supports symmetric multiprocessing (SMP). 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 your 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.

Your IBM Netfinity 4500R server comes with a three-year limited warranty and IBM Server StartUp Support. If you have access to the World Wide Web, you can obtain upto-date information about your 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 table provides a summary of the features and specifications for your Netfinity 4500R server.

Microprocessor:

• Intel® Pentium III

• 256 KB Level-2 cache

• Supports up to two microprocessors

Memory:

•Maximum: 4 GB

• Type: ECC, SDRAM, Registered DIMMs

• Slots: 4 non-interleaved

Drives standard:

• Diskette: 1.44 MB

•CD-ROM: 24X IDE

Expansion bays:

• Hot-swap: 3 slim high

• Non-hot-swap: Two 5.25-inch

PCI expansion slots:

• Three 33 MHz/64-bit

• Two 33 MHz/32-bit

Hot-swap power supplies:

• 270 Watt (115-230 Vac)

•Minimum: One

• Maximum: Two, second power supply provides redundant power

Redundant cooling:

• Three hot-swap fans

Video:

•S3 video controller

• Compatible with SVGA and VGA

•8 MB video memory

Size (Rack Model)

• Height: 13.4 mm (5.25 in.)

• Depth: 66.1 mm (26 in.)

• Width: 41.5 mm (16.3 in.)

• Weight: 22.7 to 29.5 (50 to 65lbs.) depending upon configuration

Integrated functions:

• Netfinity Advanced System Management processor

• Dual channel Ultra SCSI controller (two internal channels)

• 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: 5.9 bel maximum

• Sound power, operating: 6.1 bel maximum

• Sound pressure, operating: 47.5 dBa maximum

Environment:

• Air temperature: — Server on: 10º to 35º C (50º to 95º F). Altitude: 0 to 914 m (2998 ft.)

— Server on: 10º to 32º C (50º to 89.6º F). Altitude: 914 m (2998 ft.) to 2133 m

(6998 ft.)

— Server off: 10º to 43º C (50º to 109.4º F). Maximum altitude: 2133 m (6998 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 configuratrion 375 BTU (110 watts) — Maximum configuration 897.4 BTU (375 watts)

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

• Input kilovolt-amperes (kVA) approximately: — Minimum: 0.08 kVA

4 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Server features

— Maximum: 0.52 kVA

The Netfinity 4500R server is designed to be cost-effective, powerful, and flexible. Your server offers:

• Impressive performance using an innovative approach to SMP Your server supports up to two Intel Pentium III microprocessors. Your server

comes with one microprocessor installed; you can install an additional microprocessor to enhance performance and provide SMP capability.

• Large data-storage and hot-swap capabilities All models of the server support up to three hot-swap hard disk drives. This hot-

swap feature enables you to remove and replace hard disk drives without turning off the server. A 3-Pack hard-disk drive option is available to add an additional three drive bays.

• Optional PCI adapters Your server uses peripheral component interconnect (PCI) bus architecture to

provide compatibility with a wide range of existing hardware devices and software applications. Your server supports up to five PCI adapters in the expansion slots on the system board.

• Redundant cooling capability The redundant cooling capability of the hot-swap fans in your server allow

continued operation if one of the fans fails. You can also replace a failing hot-swap fan without turning off the server.

• Optional redundant power capability You can install an additional 270-watt power supply in your server to provide

redundant power for your server. The Power Non-Redundant light emitting diode (LED) in the group of diagnostic LEDs on the system board is lit when the power load is 270 watts or greater with two power supplies installed.

• Large system memory The memory bus in your server supports up to 4GB of system memory. The

memory controller provides error correcting code (ECC) support for up to four industry standard PC133, 3.3 V, 168-pin, 8-byte, registered, synchronousdynamic-random access memory (SDRAM) dual inline memory modules (DIMMs) (Intel PC-Registered SDIMM Specifications, Revision 1.0 or later).

• System-management capabilities Your server comes with an Advanced System Management Processor on the

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

Note: The Advanced System Management Processor is sometimes referred to as

the service processor.

• Integrated network environment support Your server comes with an Ethernet controller on the system board. This Ethernet

controller has an interface for connecting to 10-Mbps or 100-Mbps networks. The server automatically selects between 10BASE-T and 100BASE-TX. The controller provides full-duplex (FDX) capability, which allows simultaneous transmission and reception of data on the Ethernet local area network (LAN).

General information 5

• Redundant network-interface card The addition of an optional, redundant network interface card (NIC) provides a

failover capability to a redundant Ethernet connection. If a problem occurs with the primary Ethernet connection, all Ethernet traffic associated with this primary connection is automatically switched to the redundant NIC. This switching occurs without data loss and without user intervention.

• Optional digital linear tape drive The addition of an optional digital linear tape drive (DLT) allows quick backup of

large amounts of data.

• IBM ServerGuide CDs The ServerGuide CDs included with your Netfinity servers provide programs to

help you set up your server and install the network operating system (NOS). The ServerGuide program detects the hardware options installed, and provides the correct configuration programs and device drivers. In addition, the ServerGuide CDs include a variety of application programs for your server. See SERVERGUIDE for more information.

Reliability, availability, and serviceability features

Three of the most important features in server design are reliability, availability, and serviceability (RAS). These factors help to ensure the integrity of the data stored on your server; that your server is available when you want to use it; and that should a failure occur, you can easily diagnose and repair the failure with minimal inconvenience.

The following is an abbreviated list of the RAS features that your server supports.

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

• Power-on self-test (POST)

• Integrated Netfinity Advanced System Management Processor

• Predictive failure alerts

• System auto-configuring from configuration menu

• Remote system problem-determination support

• Power and temperature monitoring

• Fault-resilient startup

•Hot-swap drive bays

• Error codes and messages

• System error logging

• Upgradable BIOS, diagnostics, and Netfinity Advanced System Management Processor code

• Automatic restart after a power failure

• Parity checking on the SCSI and PCI buses

• Error checking and correcting (ECC) memory

• Redundant hot-swap power supply option

• Redundant hot-swap cooling option

• Redundant Ethernet capabilities (with optional adapter)

• Vital Product Data (VPD) on processor complex, system board, power backplane, SCSI backplane, and each power supply

• Operator information panel and group of diagnostic LEDs on the system board

• Remote Connect

6 Hardware Maintenance Manual: Netfinity 4500R Type 8656

CAUTION:

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

Controls and indicators

The most commonly used controls and status indicators are on the front panel of the server.

򍦠1򐂰 AC power light 򍦠2򐂰 Hard Disk Status light 򍦠3򐂰 Hard disk Activity light 򍦠4򐂰 System power light 򍦠5򐂰 Power control botton 򍦠6򐂰 Reset button

System Power Light: 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.

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 or from the UPS.

Power Control Button: Press this button to manually turn the server on or off.

General information 7

CAUTION:

You can start the server in several ways:

• You can turn on the server by pressing the Power Control button on the front of the server.

Note: After you plug the power cord of your server into an electrical 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.

• If the server is turned on, a power failure occurs, and unattended- start mode is enabled in the Configuration/Setup utility program, the server will start automatically when power is restored.

• If AC power is present, the server is off, and the wake-up feature is enabled in the Configuration/Setup utility program, the wake-up feature will turn on the server at the set time.

• If AC power is present, the server is off, and ring signal detect is enabled in the Configuration/Setup utility program, you can turn on the server by telephone input.

• The Netfinity Advanced System Management Processor can also turn on the server.

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. Pressing the Power Control button starts an orderly shutdown of the operating system, if this feature is supported by your operating system, and places the server in standby mode.

Note: After turning off the server, wait at least 5 seconds before pressing the

Power Control button to power the server on again.

• You can press and hold the Power Control button for more than 4 seconds to cause an immediate shutdown of the server and place the server in standby mode. You can use this feature if the operating system hangs.

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

system to stop running. Watch for the System Power light on the operator information panel to stop blinking.

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

8 Hardware Maintenance Manual: Netfinity 4500R Type 8656

AC Power Light: This light provides status information about the power supply. During normal operation, both the AC and DC Power lights are on. For any other combination of lights, see “Power supply LED errors” on page 121.

Operator Information Panel: The lights on this panel give status information for your server. See “Operator information panel” for more information.

DC Power Light: This light provides status information about the power supply. During normal operation, both the AC and DC Power lights are on. For any other combination of lights, see “Power supply LED errors” on page 121 .

Hard Disk Status Light: Each of the hot-swap drive bays has a Hard Disk Status light. When this amber light is on continuously, the drive has failed. When the light flashes slowly (one flash per second), the drive is being rebuilt. When the light flashes rapidly (three flashes per second), the controller is identifying the drive.

Hard Disk Activity Light: Each of the hot-swap drive bays has a Hard Disk Activity light. When this green light is flashing, the controller is accessing the drive.

Operator information panel

LINK

򍦠1򐂰 SCSI Hard Disk Drive Activity light 򍦠2򐂰 Ethernet Link Status light 򍦠3򐂰 Ethernet Transmit/Receive Activity light 򍦠4򐂰 Information light 򍦠5򐂰 System Error light

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

General information 9

Ethernet Transmit/Receive Activity Light: When this green light is on, there is transmit or receive activity to or from the server.

Information Light: This amber light is on when the information log contains information about certain conditions in your server that might affect performance. For example, the light will be on if your server does not have redundant power. A light on the diagnostic LED panel on the system board will also be on.

System Error Light: This amber light is lit when a system error occurs. An LED on the diagnostic LED panel will also be on to further isolate the error.

10 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Diagnostics

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

Diagnostic tools overview

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

• POST beep codes, error messages, and error logs

The power-on self-test (POST) generates beep codes and messages to indicate successful test completion or the detection of a problem. See “POST” on page 12 for more information.

• Diagnostic programs and error messages

The server diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of your server. See “Diagnostic programs and error messages” on page 13 for more information.

• Light path diagnostics

Your server has light-emitting diodes (LEDs) to help you identify problems with server components. These LEDs are part of the light-path diagnostics that are built into your server. By following the path of lights, you can quickly identify the type of system error that occurred. See “Light path diagnostics” for more information.

Identifying problems using LEDs

Your 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 of lights, you can identify the type of system error that occurred. See the following sections for more information.

Power supply LEDs

The AC and DC Power LEDs on the power supply provide status information about the power supply. See “Power supply LED errors” on page 121.

Light path diagnostics

You can use the light path diagnostics built into your server to quickly identify the type of system error that occurred. The diagnostics panel is under the "wind tunnel." Your server is designed so that any LEDs that are illuminated remain illuminated when the server shuts down as long as the AC power source is good and the power supplies can supply +5V dc current to the server. This feature helps you isolate the problem if an error causes the server to shut down. See “Light path diagnostics table” on page 12.

Diagnostics panel

The following illustration shows the LEDs on the diagnostics panel on the system board. See “Light path diagnostics table” for information on identifying problems using these LEDs.

PS1

PS2

PS3

NON

OVER

NMI

TEMP

FAN

MEM

CPU

PCI A

PCI B

VRM

DASD1

DASD2

POST

Light path diagnostics table

The System Error LED on the operator information panel is lit when certain system errors occur. If the System Error LED on your server is lit, use the following table to help determine the cause of the error and the action you should take. See table in “Information panel system error LED” on page 114.

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 your operating system or application program appears, and the System POST Complete (OK) light is illuminated on the operator information panel.

If POST detects a problem, more than one beep sounds and an error message appears on your screen. See “Beep symptoms” on page 111 and “POST error messages” on page 13 for more information.

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.

12 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

POST error messages

The table,“POST error codes” on page 122, provides information about the POST error messages that can appear during startup.

Event/error logs

The POST error log contains the three most recent error codes and messages that the system generated during POST. The System Event/Error Log contains all 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 Configuration/Setup Utility program; then, select Event/Error Logs from the main menu.

Small computer system interface messages

The following table lists actions to take if you receive a SCSI error message. Note: If your server does not have a hard disk drive, ignore any message that

indicates that the drive is not installed.

You will get these messages only when running the SCSISelect Utility. See “SCSI error codes” on page 128.

Diagnostic programs and error messages

The server diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of your server.

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 is the three-digit function code that indicates the function being tested when

the error occurred. For example, function code 089 is for the microprocessor.

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

encountered. (These codes are for trained service personnel and are described in the Hardware Maintenance Manual.)

Diagnostics 13

iii is the three-digit device ID. (These codes are for trained service personnel and

are described in the Hardware Maintenance Manual.)

date is the date that the diagnostic test was run and the error recorded. cc is the check digit that is used to verify the validity of the information. text message

is the diagnostic message that indicates the reason for the problem.

Text messages

The diagnostic text message format is as follows:

Function Name: Result (test specific string)

where:

Function Name

is the name of the function being tested when the error occurred. This corresponds to the function code (fff) given in the previous list.

Result can be one of the following: Test Specific String

This is additional information that you can use to anayze the problem.

Passed This result occurs when the diagnostic test completes without any errors. Failed This result occurs when the diagnostic test discovers an error. User Aborted

This result occurs when you stop the diagnostic test before it 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.

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

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.

14 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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.

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 either no mouse or a USB mouse

attached to your server, you will not be able to navigate between test categories using the Next Cat and Prev Cat buttons. All other functions provided by mouse-selectable buttons are also available using the function keys.

d. You can test the USB keyboard by using the regular keyboard test. The

regular mouse test can test a USB mouse. Also, you can run the USB hub test only if there are no USB devices attached.

e. You can view server configuration information (such as system configuration,

memory contents, interrupt request (IRQ) use, direct memory access (DMA) use, device drivers, and so on) by selecting Hardware Info from the top of the screen.

When the tests have completed, you can view the Test Log by selecting Utility from the top of the screen.

If the hardware checks out OK but the problem persists during normal server operations, a software error might be the cause. If you suspect a software problem, refer to the information that comes with the software package.

Viewing the test log

The test log will not contain any 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 your 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 116.

Attention: If diagnostic error messages appear that are not listed in the tables, make sure that your server has the latest levels of BIOS, Advanced System.

Diagnostics 15

Recovering BIOS

If your BIOS has become corrupted, such as from a power failure during a flash update, you can recover your 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:

The flash memory of your server contains a protected area that cannot be overwritten. The recovery boot block is a section of code in this protected area that enables the server to start up and to read a flash diskette. The flash utility recovers the system BIOS from the BIOS recovery files on the diskette.

To rec ove r the BIO S:

1. Turn off the server and peripheral devices and disconnect all external cables and

2. Locate the boot-block jumper block (J37) on the system board.

3. Place a jumper on pins 1 and 2 to enable BIOS recovery mode.

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

5. Restart the server.

6. Remove the flash diskette from the diskette drive.

7. Turn the server off.

8. Remove the jumper on the boot-block jumper block or move it to pins 2 and 3 to

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

• Use the ServerGuide program to make a BIOS flash diskette.

• Download a BIOS flash diskette from the World Wide Web. Go to http://www.pc.ibm.com/support/, select IBM Server Support, and make the selections for your server.

• Contact your IBM service representative.

power cords; then, remove the cover.

The Recovery Boot screen will appear. A progress report, Loading data from diskette xx%, is displayed. When programming is underway, a further progress report, Programming block n of 7 yy%, is displayed. When recovery is complete,

Recovery complete, remove the diskette and return boot block switch to the off position before rebooting is displayed.

return to normal startup mode.

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.

16 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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 bad connector or cable, or a problem with the hub.

— The Ethernet Transmit/Receive Activity light illuminates when the Ethernet

controller sends or receives data over the Ethernet Network. If the Ethernet Transmit/Receive Activity light is off, make sure that the hub and network are operating and that the correct device drivers are loaded.

— The Ethernet Speed 100 Mbps light illuminates when the Ethernet controller

LAN speed is 100 Mbps.

• Make sure that you are using the correct device drivers, supplied with your server.

• Check for operating system-specific causes for the problem.

• Make sure that the device drivers on the client and server are using the same protocol.

• Test the Ethernet controller. How you test the Ethernet controller depends on which operating system you are

using (see the Ethernet controller device driver README file).

Ethernet controller troubleshooting chart

You can use the following troubleshooting chart to find solutions to 10/100 Mbps Ethernet controller problems that have definite symptoms.

Diagnostics 17

Table 1. Ethernet troubleshooting chart.

Ethernet controller problem Suggested Action

The server stops running when loading device drivers.

Ethernet Link Status light does not light.

The PCI BIOS interrupt settings are incorrect.

Check the following:

• Determine if the interrupt (IRQ) setting assigned to the Ethernet controller is also assigned to another device in the Configuration/Setup Utility program.

Although interrupt sharing is allowed for PCI devices, some devices do not function well when they share an interrupt with a dissimilar PCI device. 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 We b.

• Run the network diagnostic program.

If the problem remains, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

Check the following:

• Make sure that the hub is turned on.

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

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

• Use another port on the hub.

• If the hub does not support auto-negotiation, 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.

If the problem remains, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs. .

The Ethernet Transmit/Receive Activity light does not light.

Data is incorrect or sporadic. Check the following:

Check the following: Note: The Ethernet Transmit/Receive Activity LED illuminates only when data is

sent to or by this Ethernet controller.

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

• The network might be idle. 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.

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

18 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Table 1. Ethernet troubleshooting chart.

Ethernet controller problem Suggested Action

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

The Ethernet controller stopped working without apparent cause.

Check the following:

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

• Make sure that your PCI system BIOS is current.

• Reseat the adapter.

• Determine if the interrupt (IRQ) setting assigned to the Ethernet adapter is also assigned to another device in the Configuration/Setup Utility program.

If the problem remains, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

Check the following:

• Run diagnostics for the Ethernet controller.

• Try a different connector on the hub.

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

If the problem remains, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

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 2. Novell NetWare or IntraNetWare ODI driver messages for the Ethernet controller.

PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.

Explanation: The user entered an incorrect parameter keyword. Action: Reload the driver using the correct keyword.

Diagnostics 19

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

PCNTNW-NW-054 The adapter did not respond to the initialization command.

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

it. Action: Verify that the Ethernet controller is enabled. If the Ethernet controller is enabled, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

PCNTNW-NW-058 The adapter did not respond to the initialization command.

Explanation: The interrupt request (IRQ) setting might not be valid or the

EEPROM information might be incorrect. Action: Make sure the IRQ settings are correct in the Configuration/Setup Utility program. for information on setting the interrupt requests. If the IRQ settings are correct, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

PCNTNW-NW-066 The cable might be disconnected from the adapter.

Explanation: T h e c a b l e m i g h t b e d i s c o n n e c t e d f r o m t h e s e r v e r E t h e r n e t p o r t . Action: Verify that a cable is connected to the Ethernet port.

PCNTNW-NW-071 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 14 to run the diagnostic programs..

PCNTNW-NW-072 A resource tag is unavailable.

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

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

PCNTNW-NW-073 Unable to allocate memory

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

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

PCNTNW-NW-074 The hardware interrupt cannot be set.

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

The attempt was not successful. Action: Veri fy tha t th e Ethernet controller is enabled. If the Ethernet controller is enabled, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

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

PCNTNW-NW-075 The Multiple Link Interface Driver (MLID) cannot be registered with the

Link Support Layer (LSL).

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

the LSL. Action: Check the version of the NetWare or IntraNetWare Operating System. Make sure that this driver is correct for the version of NetWare or IntraNetWare that you are using. Restart the server.

20 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

PCNTNW-NW-079 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 14 to run the diagnostic programs. .

PCNTNW-NW-086 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 14 to run the diagnostic programs.

PCNTNW-NW-087 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 14 to run the diagnostic programs.

PCNTNW-NW-091 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 your hardware configuration matches the software settings.

PCNTNW-NW-126 The group bit in the node address override was cleared.

Explanation: The IEEE address has a group bit that indicates that an address

belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. 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.

PCNTNW-NW-127 The local bit in the node address override was set.

Explanation: The local bit in the IEEE address format indicates that the

addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit must be set. You entered an address without the local bit set. The driver has set the local bit. Action: None necessary, message is for information only.

PCNTNW-NW-164 The device was not found.

Explanation: The driver cannot find an Ethernet controller in the server. Action: Verify that the Ethernet controller is enabled. If the Ethernet

controller is enabled, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

PCNTNW-NW-165 The device was not found at IOADDRESS.

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

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

PCNTNW-NW-167 PCI scan specified, device not found.

Diagnostics 21

Explanation: T h e d r i v e r c a n n o t l o c a t e t h e E t h e r n e t c o n t r o l l e r o n t h e P C I b u s . Action: Verify that the Ethernet controller is enabled. If the problem persists,

go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

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

PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.

Explanation: The Ethernet controller does not require a DMA setting. Action: None necessary, message is for information only.

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

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

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

PCNTND-1 Unable to open the Protocol Manager.

Explanation: The NDIS stack is not configured correctly. Action: Check

and correct your configuration.

PCNTND-6 Out of memory while allocating buffers.

Explanation: The driver could not allocate the requested buffers. Action:

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

PCNTND-7 A Protocol Manager device error occurred.

Explanation: The NDIS stack is not configured correctly. Action: Check

and correct your configuration.

PCNTND-8 Bad status for the Protocol Manager.

Explanation: Th e N D I S s t a c k i s n o t c o n f i g u r e d c o r r e c t l y i n t h e P R O T O C O L . I N I f i l e . Action: Check and correct your configuration.

PCNTND-9 Cannot find the PROTOCOL.INI entry.

Explanation: The NDIS stack is not configured correctly in the PROTOCOL.INI file. Action: Check and correct your configuration.

PCNTND-10 The Protocol Manager Input Output Control (IOCTL) failed.

Explanation: The NDIS stack is not configured correctly in the PROTOCOL.INI file. Action: Check and correct your configuration.

PCNTND-11 Protocol Manager registration failed.

Explanation: The NDIS stack is not configured correctly. Action: Check

and correct your configuration.

PCNTND-15 Device not found.

Explanation: The driver cannot find an Ethernet controller in the server. Action:

Verify that the Ethernet controller is enabled. If the Ethernet controller is enabled, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

PCNTND-16 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 Ethernet controller is enabled, go to “Starting the diagnostic programs” on page 14 to run the diagnostic programs.

22 Hardware Maintenance Manual: Netfinity 4500R Type 8656

+ 162 hidden pages

IBM Netfinity 4500R Type 8656, 8656 Hardware Maintenance Manual

Specifications and Main Features

Frequently Asked Questions

User Manual