IBM Netfinity 4500R Type 8656, 8656 Hardware Maintenance Manual

Download

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

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

PCNTND-21 The adapter failed the checksum test.

Explanation: The driver cannot find an Ethernet controller. Action: Ve ri f y

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

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 Configuration/Setup Utility program.

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

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.

Diagnostics 23

Table 4. NDIS (Windows NT) driver messages for the Ethernet controller.

PermaNet Server: 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 5. 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.

pnt0-6 Cannot allocate memory for the adapter during an interrupt. Please check your 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.

pnt0-7 Cannot allocate memory for the adapter during reset. Please check your 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!

Explanation: The driver cannot find an Ethernet controller. Action: Ve rif y t ha t

the Ethernet controller is enabled. If the Ethernet controller is enabled, run the diagnostic programs.

pnt0-12 Device failed checksum test!

Explanation: The driver cannot find an Ethernet controller. Action: Ve rif y t ha t

the Ethernet controller is enabled. If the Ethernet controller is enabled, run the diagnostic programs.

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 your hardware settings.

pnt0-14 Cannot locate hardware.

Explanation: The SunSoft Solaris driver cannot find any Ethernet controller. Action: Ver if y

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

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.

24 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Table 5. UNIX LLI driver messages for the Ethernet controller.

pnt0-17 Device fault...Reset initiated!

Explanation: The SunSoft Solaris driver has been reset due to a device fault. Action: Ve ri fy

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.

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

• Modify your hardware settings.

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

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

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

• Modify your hardware settings.

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

pnt0-22 add_intr_handler failed! Out of range IPL.

Explanation: The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts

with other devices in the server. Action: Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-23 add_intr_handler failed! Vector already occupied.

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

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

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

• Modify your hardware settings.

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

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

Explanation: The IBM Netfinity 10 /100 Faul t Tolerant Adapter does n ot 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 your 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 25

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 power on (see "Minimum operating requirements" on page 133).

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 configuration required for a system to power up (see page 133). For specific problems, see“Power error messages” on page 129.

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 10L6432 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: Before you begin be sure to read “Before you begin” on page 45. Follow any

special handling and installation instructions supplied with the replacement battery.

Note: After you replace the battery, you must reconfigure your server and reset the

system date and time.

To replace the battery:

26 Hardware Maintenance Manual: Netfinity 4500R Type 8656

1. Review the information in “Before you begin” on page 45 and any special handling and installation instructions supplied with the replacement battery.

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

3. Remove the battery: a. Use one finger to lift the battery clip over the battery. b. Use one finger to slightly slide the battery from its socket. The spring

mechanism behind the battery will push the battery out toward you as you slide it from the socket.

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.

4. Insert the new battery: a. Tilt the battery so that you can insert it into the socket, under the battery clip. b. As you slide it under the battery clip, press the battery down into the socket.

5. Reinstall the server cover and connect the cables. Note: Wait approximately 20 seconds after you plug the power cord of your

server into an electrical outlet for the Power Control button to become active.

6. Turn the server on.

7. Start the Configuration/Setup Utility program and set configuration parameters.

• Set the system date and time.

• Set the power-on password.

• Reconfigure your server.

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

Diagnostics 27

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

For more information on specific temperature error messages, see “Tempera ture error messages” on page 128.

28 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Configuring the server

The following configuration programs are provided with your server:

• Configuration/Setup Utility

This Configuration/Setup Utility program is part of the basic input/output system (BIOS) that comes with your 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. See “Using the SCSISelect utility program” on page 36 for more information.

• 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 your server to configure the server hardware and simplify your network operating system installation. The ServerGuide CDs also contain a collection of application programs, which you can install after your server is up and running. See “Server features” on page 5“ for more detailed information.

• ServeRAID programs

The ServeRAID programs come with the optional ServeRAID adapters and with server models that have a ServeRAID adapter preinstalled. If your server has a ServeRAID adapter installed, you must use the ServeRAID Configuration program to define and configure your disk-array subsystem before you install your operating system. See “Configuring the server”“Chapter 5. Using IBM ServeRAID,” on page 29 for more detailed information.

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.

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 - © IBM Corporation 2000

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

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

30 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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.

• Date and Time

Select this choice to set the system date and time and to change the system time sent to the Configuration/Setup Utility (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 (Configuration/Setup Utility) 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 Configuration/Setup Utility 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:

— Power-on Password

Select this choice to set or change a power-on password. See “Using passwords” on page 34 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 34 for more information.

— System Owner’s Name

Select this choice to specify a system owner's name, which will display during POST. You can remove or change the name only from the System Security menu. You can use any combination of up to 16 characters for the system owner's name.

• Start Options

Configuring the server 31

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.

You also can select which PCI SCSI adapter is given boot precedence. The first drive that is attached to the selected adapter will be assigned drive number 80L and the operating system will start from that drive. The default for boot precedence is Disabled. The range of choices depends upon the number of PCI SCSI adapters installed in the server.

You can enable a virus-detection test that checks for changes in the master boot record at startup. You also can choose to run POST in the enhanced mode or the quick mode.

• 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 Configuration/Setup Utility main menu.

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.

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

— 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 writethrough (WT). Selecting write-back mode will provide the maximum system performance.

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

32 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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 integrated SCSI, video, and Ethernet controllers. You can also enable or disable PCI slots from this menu.

– The default setting is Enable for all the controllers and 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.)

– 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. However, turning the server off and on three times results in a default startup that enables video again.

— Memory Settings

Select this choice to manually disable or 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.

• System Service Processor Settings

Select this choice to view the interrupt-request setting (IRQ) used by the Configuration/Setup Utility (system service processor). You can then use the arrow keys to select a new IRQ setting for the Configuration/Setup Utility from the list of available choices.

• Event/Error Logs

Select this choice to view or clear error logs.

— Select Clear error logs to clear the error or event log. — Select POST Error Log to view the three most recent error codes and

messages that the system generated during POST.

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

• Save Settings

Configuring the server 33

Select this choice to save your customized settings.

• Restore Settings Select this choice to delete your changes and restore the previous settings.

• Load Default Settings Select this choice to cancel your 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 system to start the operating system. 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 your power-on password. Keep a record of your password in a secure place. If you forget the power-on password, you can regain access to the server through one of the following methods:

• If an administrator password is set, enter the administrator password at the power-on prompt. Start the Configuration/Setup Utility program and change the power-on password.

• Change the position of the password override switch as described in “Setting the password override switch”.

• Remove the battery and then install the battery.

Setting the password override switch: The following illustration shows the location of the password override switch (switch 8 on switch block 1) on the system board.

Note: As shown in the illustration, switch 8 is the one at the top of the switch block.

34 Hardware Maintenance Manual: Netfinity 4500R Type 8656

򍦠1򐂰 PCI slot 5 64-bit (J44) 򍦠2򐂰 PCI slot 4 64-bit (J39) 򍦠3򐂰 PCI slot 3 64-bit (J34) 򍦠4򐂰 PCI slot 2 32-bit (J32) 򍦠5򐂰 PCI slot 1 32-bit (J27)

To set the password override switch:

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

2. Turn off the server and peripheral devices and disconnect all external cables and power cords; then, remove the cover. See “Removing the cover and bezel” on page 47.

3. Change the setting of the password override switch (switch 8 on switch block 1 on the system board) to ON.

4. Install the server cover (see “Installing the server cover and bezel” on page 60) and connect all external cables and power cords.

Note: You can now start the Configuration/Setup utility program and change the

power-on password. If you want the server to ask for a password when you turn on the server, set the password override switch back to the OFF position.

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.

Configuring the server 35

Table 6. Power-on and administrator password features.

Type of password Results

Power-on password • Enter the password to complete the system startup.

• All choices are available on the Configuration/Setup Utility main menu.

Administrator password • No password is required to start the system.

• Enter the password to access the Configuration/Setup Utility program.

• All choices are available on the Configuration/Setup Utility main menu.

Administrator and power-on password

• 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

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

Note: If your 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 your

monitor permits).

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

36 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

— 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 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. These options include enabling support for large hard disk drives and support for drives with UltraSCSI speeds.

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

• Format Disk Attention: The Low-Level Format program erases all data and programs.

Configuring the server 37

Select this choice to perform a low-level format on a hard disk drive. Depending on the hard disk drive capacity, the Low-Level Format program could take up to two hours.

Use the Low-Level Format program:

— When you are installing software that requires a low-level format — When you get recurring messages from the diagnostic tests directing you to

run the Low-Level Format program on the hard disk drive

— As a last resort before replacing a failing hard disk drive

Note: If your server has a PCI RAID adapter installed, refer to the RAID adapter

documentation for instructions for performing low-level formats on hard disk drives attached to the adapter.

To start the Low-Level Format program:

1. If the hard disk is working, make a backup copy of all the files and programs on the hard disk drive. (See your operating system information for instructions.)

2. Select Format Disk; then, follow the instructions on the screen. Note: Hard disks normally contain more tracks than their stated capacity (to

allow for defective tracks). A message appears on the screen if the defect limit is reached. If this happens, have the system serviced.

38 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Installing options

This chapter provides instructions to help you add options to your server. Some option-removal instructions are provided, in case you need to remove one option to install another.

Exploded view of the Netfinity 4500R

The orange color on components and labels in your server identifies hot-swap or hotplug components. This means that you can install or remove the components while the system is running, provided that your system is configured to support this function. For complete information about installing or removing a hot-swap or hotplug component, see the information provided in the detailed procedures in this document under “Installing a hot-swap drive” on page 52.

The blue color on components and labels indicates touch points where a component can be gripped, a latch moved, and so on.

򍦠1򐂰 Slim HDD bezel filler assembly 򍦠2򐂰 Hard disk drive tray 򍦠3򐂰 Power Supply 򍦠4򐂰 Filler panel for the power supply bay 򍦠5򐂰 Filler panel for the device bay 򍦠6򐂰 System board 򍦠7򐂰 Term ina tor Card 򍦠8򐂰 DIMM 򍦠9򐂰 Microprocessor

򍦠10򐂰 Air baffle 򍦠11򐂰 Rear fan

System board layout

The illustrations in the following sections show the components on the system board.

System board options connectors

The following illustration shows a layout of the system board and identifies systemboard connectors for user-installable options.

򍦠1򐂰 PCI slot 5 32-bit (J44) 򍦠2򐂰 Battery 򍦠3򐂰 PCI slot 4 32-bit (J39) 򍦠4򐂰 PCI slot 3 64-bit (J34) 򍦠5򐂰 PCI slot 2 64-bit (J32) 򍦠6򐂰 PCI slot 1 64-bit (J27) 򍦠7򐂰 DIMM 1 (J23) 򍦠8򐂰 DIMM 2 (J21) 򍦠9򐂰 DIMM 3 (J19) 򍦠10򐂰 DIMM 4 (J18) 򍦠11򐂰 Primary microprocessor (U17) 򍦠12򐂰 Secondary microprocessor (U3) 򍦠13򐂰 Voltage regulator module 2 (VRM2) (U26)

40 Hardware Maintenance Manual: Netfinity 4500R Type 8656

System board internal cable connectors

The following illustration shows internal cable connectors on the system board.

򍦠1򐂰 Internal SCSI channel A (J29) 򍦠2򐂰 Internal SCSI channel B (J17) 򍦠3򐂰 Fan 3 (J35) 򍦠4򐂰 Main Power (J4) 򍦠5򐂰 Power (J51) 򍦠6򐂰 Fan 1 (J59) 򍦠7򐂰 3.3V power for optional backplane (J52) 򍦠8򐂰 Power system management (J12) 򍦠9򐂰 DASD (SCSI) system management (J5) 򍦠10򐂰 Fan 2 (J60) 򍦠11򐂰 Operator information panel (J50) 򍦠12򐂰 On-off / Reset panel (J38) 򍦠13򐂰 IDE (J31) 򍦠14򐂰 Diskette (J26)

System board external port connectors

The following illustration shows the external port connectors in the system board.

Installing options 41

򍦠1򐂰 Parallel port (J22) 򍦠2򐂰 Video / Advanced System Management Process or port (J13) 򍦠3򐂰 USB ports (J11) 򍦠4򐂰 Ethernet ports (J9) 򍦠5򐂰 Keyboard / mouse port (J6) 򍦠6򐂰 Serial ports (J3)

System board switches and jumpers

The following illustration identifies the switches and jumpers on the system board.

42 Hardware Maintenance Manual: Netfinity 4500R Type 8656

򍦠1򐂰 System board switch block (SW1) 򍦠2򐂰 Boot block jumper (J37)

System board jumper blocks

Any jumper blocks on the system board that are not shown in the illustration are reserved. For normal operation of the system, no jumpers should be installed on any of the jumper blocks. See “Recovering BIOS” on page 16 for information about the boot block jumper.

System board switch block

The switch block contains microswitches 1-8. As shown in this illustration, switch 8 is at the top of the switch block and switch 1 is at the bottom.

The following table describes each switch.

Table 7. Switches 1-8.

Switch number Description

1- 4 Microprocessor speed setting. See Table 8 on page 44.

5 Power-on override.

When On, overrides the power-on switch and forces power-on mode. The system will always boot without the use of the power-on switch. The default setting is Off (disabled).

6 Clock frequency selection.

7 Reserved. The default setting is Off.

Installing options 43

When On, sets the host bus speed to 100 MHz. When Off, the host bus speed is 133 MHz. The default setting is Off.

Table 7. Switches 1-8.

Switch number Description

8 Password override.

When On, bypass the power-on password. When Off, require the user to enter the power-on password at startup, if one is set. The default setting is Off.

Table 8. Microprocessor speed settings.

Microprocessor speed

667/133 On On Off Off

733/133 On Off Off Off

800/133 Off On On On

866/133 Off Off On On

Note: The speed settings shown above apply only to unlocked processors. If the

processors are production level they are locked and there is no need to change the speed settings.

System board LED locations

The following illustration identifies LEDs on the system board. You might need to refer to this figure when solving problems with the server.

Switch 1 Switch 2 Switch 3 Switch 4

򍦠1򐂰 Secondary microprocessor failure (CR7) 򍦠2򐂰 Primary microprocessor failure (CR1) 򍦠3򐂰 Voltage regulator module (VRM2) failure (CR16) 򍦠4򐂰 Integrated voltage regulator (VRM1) failure (CR4)

44 Hardware Maintenance Manual: Netfinity 4500R Type 8656

򍦠5򐂰 Diagnostics panel (See Table 6) 򍦠6򐂰 Advanced System Management Processor error (CR70) 򍦠7򐂰 Power-on (CR56) 򍦠8򐂰 DIMM1 failure (CR21) 򍦠9򐂰 DIMM2 failure (CR28) 򍦠10򐂰 DIMM3 ailure (CR18) 򍦠11򐂰 DIMM4 failure (CR20)

Table 9. Diagnostics panel LEDs.

CR LED Description

29 PS1 Power supply 1 failure.

30 PS2 Power supply 2 failure.

31 PS3 Not used.

32 NON Non-redundant power.

33 OVER Overspecification. The system has exceeded the power capibilities of the installed

power supply units.

34 NMI Non-maskable-interrupt occurred.

22 TEMP System temperature exceeded maximum rating.

23 FAN A fan failed or is operating slowly.

24 MEM Memory failure. One or more dual in-line memory modules (DIMMS) failed.

25 CPU Microprocessor failure. One or both microprocessors failed.

26 PCI 1 Error on primary PCI channel (A) or system board.

27 PCI 2 Error on secondary PCI channel (B) or system board.

58 VRM Error on voltage regulator module or on integrated voltage regulator.

53 DASD1 SCSI bus A failure. The SCSI backplane (if any) or a device connected to SCSI bus

A failed.

57 DASD2 SCSI bus B failure. The SCSI hot-swap disk drive backplane on SCSI bus B failed.

Before you begin

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

• Become familiar with the safety and handling guidelines specified under “Working inside a server with power on” on page 46, “Handling static-sensitive

devices” on page 46, and read “Safety information” on page 141. These guidelines will help you work safely while working with your server or options.

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

• The orange color on components and labels in your server indentifies hot-swap or hot-plug components. This means that you can install or remove the component while the system is running, provided that your system is configured to support this function. For complete details about installing or removing a hot-swap or hotplug component, see the information provided in this chapter.

• The blue color on components and labels indentifies touch points where a component can be gripped, a latch moved, and so on.

Installing options 45

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

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

• Have a small, flat-blade screwdriver available.

• For a list of supported options for your server, 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:

• 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 cover is in place during normal operation.

• Space is available around the server to allow the server cooling system to work

properly. Refer to the documentation that comes with the rack.

• The cover is removed for no longer than 30 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.

• A failed fan is replaced within 48 hours.

Working inside a server with power on

Your server supports hot-plug, hot-add, and hot-swap devices and it is designedto 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 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, 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.

• Take care to 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.

46 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

Removing the cover and bezel

򍦠1򐂰 Cover 򍦠2򐂰 Cover release latch 򍦠3򐂰 Flanges

To remove the server top cover:

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

2. If you are planning to install or remove any part other than a hot-swap hard disk drive, hot-swap power supply, or hot-swap fan, turn off the server and all attached devices and disconnect all external cables and power cords.

3. Release the left and right side latches and pull the server out of the rack enclosure until both slide rails lock.

Note: When the server is in the locked position, you can reach the cables on the

back of the server.

4. Lift the cover-release latch and slide the top cover toward the rear of the server about 25 mm (1 inch). Lift the cover off the server and set the cover aside.

Attention: For proper cooling and airflow, replace the cover before turning on

the server. Operating the server for extended periods of time (over 30 minutes) with the cover removed might damage server components.

To remove the bezel:

1. Press in on the top sides of the bezel and pull the bezel away from the server front.

2. Store the bezel in a safe place.

Installing options 47

Working with adapters

You can install up to five peripheral component interconnect (PCI) adapters in the expansion connectors on the system board.

Your server comes with a video controller. This video controller is an integrated component on the system board. It is not removable. If you want to disable this controller and use a video adapter instead, you can install a video adapter in an expansion slot. When you install a video adapter, the server BIOS automatically disables the integrated video controller.

The following illustration shows the location of the PCI expansion slots on the system board.

򍦠1򐂰 PCI slot 5 64-bit (J44) 򍦠2򐂰 PCI slot 4 64-bit (J39) 򍦠3򐂰 PCI slot 3 64-bit (J34) 򍦠4򐂰 PCI slot 2 32-bit (J32) 򍦠5򐂰 PCI slot 1 32-bit (J27)

Adapter considerations

Before you continue with the adapter-installation procedure:

• Review the documentation that comes with the adapter and follow those instructions in addition to the instructions given in this section. If you need to change the switch or jumper settings on your adapter, follow the instructions that come with the adapter.

• You can install full-length adapters in all expansion slots.

• You can install a 32-bit RAID adapter in any of the PCI slots, but you might want

to install it in a 32-bit slot and use the 64-bit slots for 64-bit adapters.

48 Hardware Maintenance Manual: Netfinity 4500R Type 8656

• Your server supports 5.0V and universal PCI adapters; it does not support 3.3V adapters.

Note: Universal PCI adapters support both 3.3V and 5.0V operation.

• Your server uses a rotational interrupt technique to configure PCI adapters. Because of this technique, you can install a variety of PCI adapters that currently do not support sharing of PCI interrupts.

• PCI slots 1 and 2 are on primary PCI bus A and PCI slots 3, 4, and 5 are on secondary PCI bus B. The system scans PCI slots 1 through 5 to assign system resources; then the system starts (boots) the PCI devices in the following order, if you have not changed the boot precedence from the default: PCI slots 1 and 2, system board SCSI devices, and then PCI slots 3 through 5.

You can use the Configuration/Setup Utility program to change the boot precedence for your server. Select Start Options from the Configuration/Setup Utility program.

Adapter installation instructions

򍦠1򐂰 Adapter 򍦠2򐂰 Expansion-slot cover

The following illustration shows the rerouting of the SCSI cable if you install a ServerRAID adapter.

Installing options 49

򍦠1򐂰 Cable port

To install an adapter:

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

2. Turn off the server and peripheral devices and disconnect all external cables and power cords; then, remove the cover (see “Removing the cover and bezel” on page 47).

3. Determine which expansion slot you will use for the adapter. Attention: Check the instructions that come with the adapter for any

requirements or restrictions.

4. Remove the expansion-slot cover: a. Loosen and remove the screw on the top of the expansion-slot cover. b. Slide the expansion-slot cover out of the server. Store it in a safe place for

future use. Attention: Expansion-slot covers must be installed on the openings for all

vacant 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 gold-edge connectors on the

adapter.

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

8. Set any jumpers or switches as described by the adapter manufacturer.

9. 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 before you apply power. Incomplete insertion might cause damage to the system board or the adapter.

c. Insert and tighten the expansion-slot screw on the top of the adapter bracket.

10. Connect any needed cables to the adapter.

• If you are installing a ServeRAID adapter, disconnect the cable from SCSI

connector A on the system board and plug it into the connector on the top of the ServeRAID adapter.

• If you are installing an adapter that is not a ServeRAID adapter, refer to the

documentation that came with your adapter for cabling instructions.

Attention: Route cables so that the flow of air from the fans is not blocked.

11. If you have other options to install or remove, do so now; otherwise, go to “Installing the server cover and bezel” on page 60.

Installing internal drives

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

50 Hardware Maintenance Manual: Netfinity 4500R Type 8656

• Diskette

• Hard disk

• CD-ROM

• Ta pe

Your server contains hardware that lets you replace a failed hard disk drive without turning off the server. Therefore, you have the advantage of continuing to operate your system while a hard disk drive is removed or installed. These drives are known as hot-swappable or hot-swap drives.

Each hot-swap drive bay has two indicator lights (see “Controls and indicators” on page 7). If the amber hard-disk status light is lit continuously, that individual drive is faulty and needs to be replaced. When the hard-disk status light indicates a drive fault, you can replace that hot-swap drive without turning off the server.

Each hot-swap drive that you plan to install must have a hot-swap-drive tray attached. The drive must have a single connector attachment (SCA) connector. Hotswap-drive trays come with the hot-swap drives.

Internal drive bays

Internal drives are installed in bays. Your server comes with a preinstalled diskette drive and a preinstalled CD-ROM drive.

򍦠1򐂰 CD-ROM drive 򍦠2򐂰 Diskette drive 򍦠3򐂰 How-swap bay (SCSI ID 2) 򍦠4򐂰 How-swap bay (SCSI ID 0) 򍦠5򐂰 How-swap bay (SCSI ID 1) 򍦠6򐂰 Empty 5.25-inch bays

• Your server comes with one 3.5-inch, 1.44 MB diskette drive and one IDE CDROM drive.

• The empty bays below the diskette drive come without a device installed. You can use these bays for 5.25-inch, half-high, removable-media drives, such as tape backup drives. You also can combine these bays into a single, full-high bay and install a digital linear tape (DLT) drive; or, you can install a 3-Pack Hard-Disk Drive option, which converts these bays to three hot-swap drive bays.

• The Netfinity 4500R server supports only one diskette drive.

• If you are installing a device with a 50-pin connector in either bay A or B, you

need a 68-pin to 50-pin converter (option number 32G3925).

• Your server supports three slim-high (1-inch) hot-swap hard disk drives in the hot-swap bays. If your server has the 3-Pack Bay option installed, it supports three additional hot-swap hard disk drives.

Installing options 51

• The hot-swap bays connect to a SCSI backplane. This backplane is a printed circuit board behind the bay.

Note: The server's EMI integrity and cooling are both protected by having bays A

and B covered or occupied. When you install a drive, save the filler panel from the bay, in case you later remove the drive and do not replace it with another.

SCSI drives

Some drives have a special design called small computer system interface, or SCSI. This design allows you to attach multiple drives to a single SCSI channel.

Notes:

1. Any information about SCSI drives also applies to other SCSI devices, such as tape drives.

2. If you plan to install both internal and external SCSI devices, you must follow the instructions in “Connecting external options” on page 60, in addition to the instructions in this section.

A 16-bit (wide) SCSI cable connects the SCSI hard-disk drive backplane to an integrated SCSI controller on the system board. An additional 16-bit 1-drop SCSI cable is shipped inside your server. It is folded and restrained with a cable clamp on the bottom of the server chassis near the empty bays. You can use this cable to connect an optional SCSI device installed in one of the empty 5.25-inch bays to the SCSI channel A connector on the system board.

SCSI IDs

Each SCSI device that is connected to an individual channel of a SCSI controller needs a unique identification (ID) so that the controller can identify the devices and ensure that different devices do not attempt to transfer data at the same time. If you need to set IDs for SCSI devices, refer to the instructions that come with those devices.

Your server automatically sets SCSI IDs for hot-swap hard disk drives.

The SCSI ID assigned to each hot-swap bay is shown on your server beside the bay. The server uses the hard disk drive SCSI IDs to send status information to the indicator lights above each hot-swap bay.

The processing sequence for SCSI devices is set through the SCSISelect Utility program. The default sequence proceeds from the lowest SCSI ID to the highest (0 to

15).

Ensure that the device you are installing is not terminated. It is not necessary to set termination jumpers on internal SCSI devices. The server hardware provides termination for all internal SCSI devices.

Installing a hot-swap drive

The hot-swap drive bays support hot-swap drives only.

This section gives the procedure for installing a hot-swap hard disk drive. If you want to remove a drive, reverse the following steps.

Notes:

1. To minimize the possibility of damage to the hard disk drives, install the server in the rack before installing the hard disk drives.

52 Hardware Maintenance Manual: Netfinity 4500R Type 8656

2. You do not have to turn off the server to install hot-swap drives. However, you must turn off the server when performing any steps that involve installing or removing cables.

򍦠1򐂰 Filler panel 򍦠2򐂰 Drive-tray assembly 򍦠3򐂰 Drive handle

To install a drive in a hot-swap drive bay:

1. Review the information in “Before you begin” on page 45. Attention: To maintain proper system cooling, do not operate the server for more

than two minutes without either a drive or a filler panel installed for each bay.

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

3. Install the hard disk drive in the hot-swap bay: a. Ensure the tray handle is open (that is, perpendicular to the drive). b. Align the drive/tray assembly with the guide rails in the bay. c. Gently push the drive/tray assembly into the bay until the drive connects to

the backplane.

d. Push the tray handle down until it locks.

4. Check the hard disk drive status indicators to verify that the hard disk drive is operating properly.

Installing a non-hot-swap drive

Before you install drives in your server, verify that you have all the cables and any other equipment specified in the documentation that comes with the internal drive. You might also need to perform certain preinstallation activities. Some of the steps are required only during the initial installation of an option.

Installing options 53

򍦠1򐂰 Slide rails 򍦠2򐂰 Filler panel 򍦠3򐂰 Slide rail 򍦠4򐂰 Drive 򍦠5򐂰 Slide rail

To install a non-hot-swap drive:

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

2. Turn off the server and peripheral devices and then remove the cover. (See “Removing the cover and bezel” on page 47.)

3. Remove the trim bezel.

4. Remove the filler panel from the bay opening by pulling the filler panel away from the server. You do not need the filler panel when you have a drive installed in the bay.

Note: The server's EMI integrity and cooling are protected by having the non-

hot-swap bays covered or occupied. When you install a drive, save the filler panel from the bay, in case you later remove the drive and do not replace it with another.

5. Touch the static-protective bag containing the drive to any unpainted metal surface on the server; then, remove the drive from the bag and place it on a staticprotective surface.

6. Set any jumpers or switches on the drive according to the documentation that comes with the drive.

7. Install rails on the drive.

• If you are installing a standard-size drive:

a. Pull the blue slide rails off the back of the filler panel. b. Clip the rails onto the sides of the drive.

54 Hardware Maintenance Manual: Netfinity 4500R Type 8656

• If you are installing a digital linear tape (DLT) backup drive, use the metal slide rails and screws that are shipped in the box that contains the server documentation.

8. Place the drive so that the slide rails engage in the bay guide rails. Push the drive into the bay until it clicks into place.

9. If you are installing a SCSI device, continue with the next step. If you are installing an IDE device, go to step 12..

10. To install a SCSI device: a. Attach the connector on the 1-drop SCSI cable for the non-hot-swap drive

bays to the back of the drive. The cable is shipped restrained in a cable clamp on the bottom of the server chassis near the bays. Connect the other end of the cable to SCSI channel A on the system board, if it is not already attached. See “System board internal cable connectors” on page 41 for the location of the SCSI channel A connector.

Note: If you want to install more than one optional SCSI 5.25-inch device,

install an optional SCSI adapter to control the device.

b. Connect a power cable to the back of the drive. Power cables for non-hot-

swap drives come installed in your server. The connectors are keyed and can be inserted only one way.

c. Continue with step 12.

11. To install an IDE device, such as a CD-ROM drive or a DVD-ROM drive, use the two-drop IDE cable that comes with the option:

Note: If you add an IDE device such as a CD-ROM R/W drive or a DVD-ROM

drive, you will no longer be able to use the slim-high CD-ROM that came with the system.

a. Remove the cable connecting the CD-ROM drive to the IDE connector on the

system board.

b. Using the two-drop cable that came with your IDE option, connect the IDE

device to the IDE connector on the system board.

c. Set the jumper on the back of the new IDE device to master.

12. If you have other options to install or remove, do so now; otherwise, go to “Installing the server cover and bezel” on page 60.

Installing a microprocessor

Your server comes with one microprocessor installed on the system board. If you install an additional microprocessor, your server can operate as a symmetric multiprocessing (SMP) server. With SMP, certain operating systems and application programs can distribute the processing load between the microprocessors.

Notes:

1. Before you install a new microprocessor, 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 your server is available through the World Wide Web and the IBM Bulletin Board System (BBS). The latest level of BIOS for your server is available through the World Wide Web

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

Installing options 55

3. When the second processor (microprocessor 2) is installed it becomes the BOOT processor and the original processor (microprocessor 1) becomes the application processor.

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.

򍦠1򐂰 Air baffle

򍦠1򐂰 Term ina tor card 򍦠2򐂰 Microprocessor 2 򍦠3򐂰 VRM 򍦠4򐂰 Microprocessor 1 򍦠5򐂰 VRM connector

56 Hardware Maintenance Manual: Netfinity 4500R Type 8656

򍦠6򐂰 Microprocessor 2 connector

To install an additional microprocessor:

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

2. Turn off the server and peripheral devices and disconnect all external cables and power cords; then remove the cover (see “Removing the cover and bezel” on page

47).

3. Remove the air baffle by grasping it at the sides and lifting it from the server.

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 is shipped in; you will need to install it again, if you ever remove the microprocessor.

5. 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. Center the microprocessor over the microprocessor connector and carefully

press the microprocessor into the connector.

Note: To remove a microprocessor, pull upward on the microprocessor handle.

6. Install the VRM included in the microprocessor kit. Attention: When installing or replacing a VRM, use only a VRM specified for

use with the Netfinity 4500R server. Use of other VRMs might cause your server to overheat.

a. Center the VRM over the VRM connector. Make sure that the VRM is oriented

and aligned correctly.

b. Press the VRM into the connector.

Note: If you remove the microprocessor later, remember to install the terminator

card in the appropriate microprocessor connector and to remove the VRM.

7. Install the air baffle. Make sure the sides of the air baffle fit inside the brackets on the server.

8. If you have other options to install or remove, do so now; otherwise, go to “Installing the server cover and bezel” on page 60.

Installing a hot-swap power supply

Your server comes with one power supply. You can install an additional power supply.

Note: You do not need to turn off the power to the server to install a hot-swap power

CAUTION:

Installing options 57

supply.

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.

򍦠1򐂰 Power supply 1 power cord connector 򍦠2򐂰 Power supply 2 power cord connector

򍦠1򐂰 Filler panel 򍦠2򐂰 Power supply 򍦠3򐂰 Handle 򍦠4򐂰 AC Power light 򍦠5򐂰 DC Power light

To install a power supply:

1. Remove the filler panel from the empty power supply bay by inserting your finger into the depression on the filler panel and pulling it away from the server. Save the filler panel in case you remove the power supply at a later time.

Note: During normal operation, each power-supply bay must have either a

58 Hardware Maintenance Manual: Netfinity 4500R Type 8656

power supply or filler panel installed for proper cooling.

2. Install the power supply in the bay: a. Place the handle on the power supply in the open position (that is,

perpendicular to the power supply) and slide the power supply into the chassis.

b. Gently close the handle to seat the power supply in the bay.

3. Plug the power cord for the added power supply into the power cord connector on the rear of the server.

4. Plug the power cord into a properly grounded electrical outlet.

5. Verify that the DC Power light and AC Power light on the power supply are lit, indicating that the power supply is operating correctly.

Replacing a hot-swap fan assembly

Your server comes with three hot-swap fan assemblies. You do not need to turn off the power to the server to replace a hot-swap fan assembly.

Attention: Replace a fan that has failed within 48 hours to help ensure proper cooling.

򍦠1򐂰 Handle 򍦠2򐂰 Fan 3 򍦠3򐂰 Fan 1 򍦠4򐂰 Fan 2 Error LED 򍦠5򐂰 Fan 2

To replace a hot-swap fan assembly:

1. Remove the cover. See “Removing the cover and bezel” on page 47. Attention: To ensure proper system cooling, do not remove the top cover for more

than 30 minutes during this procedure.

2. The LED on the failing fan assembly will be lit. Remove the failing fan assembly from the server by lifting the orange handle on the top of the fan assembly and and pulling the fan assembly away from the server.

3. Slide the replacement fan assembly into the server until it clicks into place.

4. Verify that the FAN LED on the diagnostics panel on the system board is not lit. If the FAN LED is lit, reseat the fan.

5. Replace the cover. See “Installing the server cover and bezel” on page 60.

Installing options 59

Installing the server cover and bezel

򍦠1򐂰 Cover 򍦠2򐂰 Cover-release latch 򍦠3򐂰 Flanges

To install the server cover:

1. Place the cover-release latch in the open (up) position and align the flanges on the left and right sides of the cover with the slots on the server chassis.

2. Close the cover-release latch.

To install the bezel:

1. Align the trim bezel with the front of the server.

2. Press inward on the top sides of the bezel and press the bezel toward the server until it clicks into place.

To complete the installation:

If you disconnected any cables from the back of the server, reconnect the cables; then, plug the power cords into properly grounded electrical outlets.

Connecting external options

If you install a SCSI adapter, you can attach a SCSI storage expansion enclosure to your server.

Cabling requirements

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, see ANSI SCSI Standards:

• X3.131-1986 (SCSI)

• X3.131-1994 (SCSI-2)

• X3T10/1071D

Adhering to these standards ensures that your server operates properly.

60 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Setting SCSI IDs for external devices

Each SCSI device that is connected to a SCSI controller must have a unique SCSI ID, so that the SCSI controller can identify the devices and ensure that different devices do not attempt to transfer data at the same time. SCSI devices that are connected to different SCSI controllers can have duplicate SCSI IDs. The SCSI controller uses one of the SCSI IDs; the default SCSI ID for the SCSI controller is 7. Refer to the instructions that come with the SCSI devices for more information about setting a SCSI ID.

Installation procedure

To attach an external device:

1. Turn off the server and all attached devices.

2. Follow the instructions that come with the option to prepare it for installation and

Input/Output ports

This section provides information about the input/output (I/O) ports on the rear of your server. These ports include the following:

• One Parallel port

• One Video port

• One Keyboard port

• One Auxiliary-device (pointing device) port

• Two Ultra3 SCSI ports

• Two Serial ports

• Two Universal Serial Bus ports

• One Ethernet port

• Three Advanced System Management ports

to connect it to the server.

򍦠1򐂰 Mouse 򍦠2򐂰 Management port C 򍦠3򐂰 Advanced System Management Interconnect knockout 򍦠4򐂰 Parallel 򍦠5򐂰 Video 򍦠6򐂰 Universal serial bus (USB) 1 and 2 򍦠7򐂰 Ethernet 򍦠8򐂰 Keyboard 򍦠9򐂰 Serial B 򍦠10򐂰 Serial A

Installing options 61

Parallel port

Your 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 ot 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 your server.

Table 10. Parallel-port connector pin-number assignments.

Pin I/O SPP/ECP Signal EPP Signal

1 O -STROBE -WRITE

2 I/O Data 0 Data 0

3 I/O Data 1 Data 1

4 I/O Data 2 Data 2

5 I/O Data 3 Data 3

6 I/O Data 4 Data 4

7 I/O Data 5 Data 5

8 I/O Data 6 Data 6

62 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Table 10. Parallel-port connector pin-number assignments.

9 I/O Data 7 Data 7

10 I -ACK -ACK

11 I BUS Y -WAIT

12 I PE (paper end) PE (paper end)

13 I SLCT (select) SLCT (select)

14 O -AUTO FD (feed) -AUTO FD

15 I -ERROR -ERROR

16 O -INIT -INIT

17 O -SLCT IN -SLCT IN

18 - Ground Ground

19 - Ground Ground

20 - Ground Ground

21 - Ground Ground

22 - Ground Ground

23 - Ground Ground

24 - Ground Ground

25 - Ground Ground

Video port

Your 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 following table shows the pin-number assignments for the 15-pin analog video connector on the rear of your server.

Table 11. Video-port connector pin-number assignments.

Pin Signal Pin Signal Pin Signal

the integrated video adapter.

1115

1 Red 6 Ground 11 Monitor ID bit 0

2 Green or monochrome 7 Ground 12 DDC SDA

3 Blue 8 Ground 13 Horizontal

Installing options 63

synchronization (Hsynch)

Table 11. Video-port connector pin-number assignments.

Pin Signal Pin Signal Pin Signal

4 Monitor ID bit 2 9 +5 V dc 14 Vertical

synchronization (Vsynch)

5 Ground 10 Ground 15 DDC SDL

Keyboard port

There is one keyboard on the rear of your 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 your server.

Table 12. Keyboard connector pin-number assignments .

Pin I/O Signal

1I/OData

2N/AReserved

3N/AGround

4 N/A +5 V dc

5 I/O Keyboard clock

6N/AReserved

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

64 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Table 13. Auxiliary-device connector pin-number assignments .

Pin Signal

1Data

2Not connected

3Ground

4+5 V dc

5Clock

6Not connected

Ultra3 SCSI ports

Your server has an integrated dual-channel Ultra3 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

You can use the external LVD SCSI channel connector, on the rear of your server, to connect different types of small computer system interface (SCSI) devices. Inside the server, a SCSI cable connects the internal SCSI channel connector to the hot-swap drive backplane.

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.

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 your 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 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 hot-swap-drive backplane controls the SCSI IDs for the internal hot-swap drive bays. However, when you attach SCSI devices to the external SCSI connector, you

Installing options 65

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.

Pin Signal Pin Signal

1 +Data 12 35 -Data 12

2 +Data 13 36 -Data 13

3 +Data 14 37 -Data 14

4 +Data 15 38 -Data 15

5 +Data P1 39 -Data P1

6 +Data 0 40 -Data 0

7 +Data1 41 -Data 1

8 +Data 2 42 -Data 2

9 +Data 3 43 -Data 3

10 +Data 4 44 -Data 4

11 +Data 5 45 -Data 5

12 +Data 6 46 -Data 6

13 +Data 7 47 -Data 7

14 +Data P 48 -Data P

15 Ground 49 Ground

16 DIFFSENS 50 Ground

17 Term power 51 Term power

18 Term power 52 Term power

19 Reserved 53 Reserved

20 Ground 54 Ground

21 +Attention 55 -Attention

22 Ground 56 Ground

23 +Busy 57 -Busy

24 +Acknowledge 58 -Acknowledge

25 +Reset 59 -Reset

26 +Message 60 -Message

27 +Select 61 -Select

66 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Pin Signal Pin Signal

28 +Control/Data 62 -Control/Data

29 +Request 63 -Request

30 +Input/Output 64 -Input/Output

31 +Data 8 65 -Data 8

32 +Data 9 66 -Data9

33 +Data 10 67 -Data 10

34 +Data 11 68 -Data 11

Serial ports

Your 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 Device 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 your server. These pin-number assignments conform to the industry standard.

Table 14. Serial-port connectors pin-number assignments.

Pin Signal Pin Signal

1 Data carrier detect 6 Data set ready

Installing options 67

Table 14. Serial-port connectors pin-number assignments.

Pin Signal Pin Signal

2 Receive data 7 Request to send

3 Transmit data 8 Clear to send

4 Data terminal ready 9 Ring indicator

5Signal ground

Universal Serial Bus ports

Your 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 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 your server.

Table 15. USB-port connector pin-number assignments.

Pin Signal

1VCC

2-Data

3+Data

4Ground

68 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Ethernet port

Your 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 your server.

Note: The 100BASE-TX Fast Ethernet standard requires that the cabling in the

network be Category 5 or higher.

Configuring the Ethernet controller

When you connect your 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 full-duplex (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 your server. If you install this NIC adapter and connect it to the same logical 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. This switching occurs without any user intervention. When the primary link is restored to an operational state, the Ethernet 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 your server. See the documentation that comes with the adapter for more information.

Considerations when combining failover and hot-plug functions: If your operating system supports hot-plug 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

Installing options 69

automatically switch back to the primary adapter when the primary adapter comes back online. See “Configuring for failover” on page 70.

Configuring for failover: The failover feature currently is supported by OS/2™, Windows NT Server, and IntraNetWare. The setup required for each operating system follows.

IBM Operating System/2 (OS/2):

Note: The OS/2 operating system does not support hot-plug operations.

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. Using the MPTS Utility program, select the driver from the list and select the Edit button.

Note: Only one driver instance needs to be loaded for each redundant pair of

Ethernet controllers.

4. Change the PermaNet Server Feature keyword to TRUE and specify the Primary and Standby slots that contain the redundant pair.The integrated controller is located in slot 2 (PCI bus A slot 2).

5. To enable the writing of messages to the IBMCOM\LANTRAN.LOG file when a failover occurs:

a. Copy the file PCNETOS2.EXE from the root directory of the diskette that is

created using the ServerGuide CDs to your hard disk drive.

b. Add the following statement to the CONFIG.SYS file:

Run=d:\path\PCNETOS2.EXE

where d and path are the drive and path to which you copied PCNETOS2.EXE.

6. Restart the server.

The failover function is now enabled.

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

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 Failover DMI Agent

2. IBM PCI Hot Plug Solution

3. IBM Netfinity 10/100 Fault Tolerant Adapter device drivers

70 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Note: The order of installation is important. You must install the IBM Netfinity Hot

Plug for Windows NT

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 Failover DMI Agent:

1. Download the DMI EXE 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 PCI Hot Plug Solution package:

1. Download the IBM PCI Hot Plug Services EXE 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.

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 bus A, slot 2.

Installing options 71

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

1. Add the redundant NIC adapter according to the instructions that are provided with the adapter.

2. Load the device driver by using the following command:

LOAD d:\path\PCNTNW.LAN PRIMARY=x SECONDARY=y

where d and path are the drive and path where the driver is located, and x and y are the PCI slot numbers where the redundant pair is located.

The slot number associated with the integrated Ethernet controller can vary depending on the configuration of the server. To determine the slot number, load the driver with no parameters. The driver will display the available slot numbers. The slot number that is greater that 10000 will be the slot number of integrated Ethernet controller. When the slot number of the integrated Ethernet controller is determined, reload the driver with the appropriate parameters.

3. When the driver is loaded, bind it to a protocol stack.

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:

LOAD d:\path\PCNTNW SCAN

72 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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.

Table 16. Ethernet RJ-45 connector pin-number assignments..

Pin Signal Pin Signal

1 Transmit data+ 5 Not connected

2 Transmit data- 6 Receive data -

3 Receive data+ 7 Not connected

4 Not connected 8 Not connected

Advanced System Management ports

Your 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 RS-485 function, use a dual RJ-45 connector.

You can attach a dedicated modem to the D-shell system-management connector on the rear of your server to communicate with the integrated Netfinity Advanced System Management Processor.

The RS-485 function uses the RJ-45 system-management connectors. This function enables you to connect the Advanced System Management Processors of several rackmounted servers so that they can communicate with each other in half-duplex mode.

Cabling the Server

The following illustration shows input/output connectors and cable routing for the server.

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

Installing options 73

򍦠1򐂰 Power supply 1 power cord connector 򍦠2򐂰 Serial A 򍦠3򐂰 Mouse 򍦠4򐂰 Universal serial bus (USB) 1 and 2 򍦠5򐂰 Management port C 򍦠6򐂰 Parallel 򍦠7򐂰 Video 򍦠8򐂰 Ethernet 򍦠9򐂰 Cable-management arm 򍦠10򐂰 Keyboard 򍦠11򐂰 Serial B 򍦠12򐂰 Power supply 2 power cord connector

Refer to the following illustration for the routing of cables through the cablemanagement arm.

74 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Netfinity Manager

Netfinity Manager provides powerful hardware systems-management 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 you to start services 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, you can access your Netfinity Manager systems from anywhere in the world.

Managing your IBM Netfinity server with Netfinity Manager

The copy of Netfinity Manager that is included with ServerGuide 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 system-management 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 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 98.

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

• If you are installing Netfinity Manager for Windows NT, see “Netfinity Manager for Windows NT system requirements” on page 77.

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 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–9MB 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

The minimum system requirements for Netfinity Manager for Windows 95 are:

• Microsoft Windows 95 or later

• Approximately 17 MB–20 MB of hard disk space (space required depends on

system configuration)

76 Hardware Maintenance Manual: Netfinity 4500R Type 8656

• A LAN adapter card and one or more of the following communications protocols: — TCP/IP (must be WinSock Version 1.1-compatible; 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 (PCOMM 4.1 or later SNA stack)

Note: Systems using Netfinity Manager with Microsoft SNA Server cannot

• A 9600 baud or greater modem (optional).

The hard disk requirement for Client Services for Netfinity Manager is 6.5 MB–9MB of hard disk space. All other system requirements are the same as for Netfinity Manager for Windows NT.

Note: Serial Connection Control will not function on systems that do not have a

properly installed and configured modem.

Netfinity Manager for Windows NT system requirements

The minimum system requirements for Netfinity Manager for Windows NT are:

• Microsoft Windows NT version 4.0 or later

• Approximately 17 MB–20 MB of hard disk space (space required depends on

system configuration)

• A LAN adapter card and one or more of the following communications protocols: — TCP/IP (must be WinSock Version 1.1-compatible; 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 (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

• A 9600 baud or greater modem (optional).

The hard disk requirement for Client Services for Netfinity Manager is 6.5 MB–9MB of hard disk space. All other system requirements are the same as for Netfinity Manager for Windows NT.

Netfinity Manager 77

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

To start the Netfinity Manager installation program on a system that is running Windows NT 4.0:

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

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.

78 Hardware Maintenance Manual: Netfinity 4500R Type 8656

4. Choose a drive and directory from which the Netfinity Manager program files will be copied.

Type in th e 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.

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

are required by the installation configuration. A window appears, displaying the

Netfinity Manager 79

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 PFA-enabled hard disk drive)

• Process Manager

• RAID Manager (requires RAID adapter)

• Remote Session

• Remote System Manager

• Remote Workstation Control

• Screen View

• Security Manager

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

80 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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.

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

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 you select the IPX or TCP/IP Network Driver.

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 NetBIOS 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 Dialup 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 you have entered all required information, 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 the User ID/Password combinations that were used when accessing remote systems. This will force you to manually log on each time a remote system is accessed.

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

Netfinity Manager 81

• 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 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 Configuration 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 you are installing Netfinity Manager for Windows 95, the installation program will display a list of changes that must be made to the CONFIG.SYS file.

Click either Ye s or No. Note: These changes must be made to the system configuration for Netfinity

Manager to run correctly.

82 Hardware Maintenance Manual: Netfinity 4500R Type 8656

• If you click Ye s 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 systemspecific 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 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 87.

• If support for ODBC database export is being installed, see “ODBC database support” on page 89.

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 information about supported version numbers refer to Table 17 on page 91.

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.

Netfinity Manager 83

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

1. Start a DB2 command window.

Note: If it is not already running, start the DB2 database manager.

2. Type the following command:

DB2 CREATE databasename ON d

where

• databasename is the name of the database

• d 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 database for ODBC, refer to “ODBC database configuration” on page 90. For information on creating the tables, refer to “Creating the Netfinity Manager tables” on page 90.

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

84 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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.

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

1. Start a DB2 command window.

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

• userid 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:

Netfinity Manager 85

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:

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.

Ty pe 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 89.

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.

86 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

1. Start a DB2 command window.

2. Type

DB2 DROP DATABASE databasename

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. Ty pe 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 89.

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.

System requirements

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 17 on page 91. See the Notes Administrator’s Guide for general system requirements and supported communications protocols.

Netfinity Manager 87

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.

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.

88 Hardware Maintenance Manual: Netfinity 4500R Type 8656

Browsing the Netfinity Manager Lotus Notes database

To browse the data contained in the Netfinity Manager Lotus Notes database:

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

System requirements

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)

— IBM DB2 For detailed information about supported ODBC platforms, see Table 17 on page

91.

Note: The ODBC database name must not be longer than 8 characters.

Netfinity Manager 89

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, NETFIN 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 Services 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.

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.

90 Hardware Maintenance Manual: Netfinity 4500R Type 8656

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

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 table shows databases and operating systems that are certified for use with this release of Netfinity Manager.

Table 17. Supported Netfinity Databases.. Reference by operating system and database client version.

Product Win 95 Win NT 3.51 Win NT 4.0 OS/2 Warp Connect OS/2 Warp 4.0

IBM DB2 Version 2.1.2 Yes Yes Yes Yes Yes

IBM DB2 Universal Database 5.0

ODBC - IBM DB2 Version 2.1.2

Netfinity Manager 91

Ye s Ye s Ye s Ye s Yes

Yes, DB 2 Driver

Yes, DB2 Driver Yes, DB2 Driver Yes, DB2 Driver Yes, DB2

Driver

Table 17. Supported Netfinity Databases.. Reference by operating system and database client version.

Product Win 95 Win NT 3.51 Win NT 4.0 OS/2 Warp Connect OS/2 Warp 4.0

ODBC - IBM DB2 Universal Database

5.0

ODBC - Microsoft SQL Vers ion 7.0

ODBC - Microsoft SQL Vers ion 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, Oracle

Oracle Version 8.0 Yes, Oracle

Yes, DB 2 Driver

Yes, Microsoft SQL Driver

Ye s Ye s Ye s Ye s Yes

Yes No Yes No No

Driver Version

2.0.3.1.1

Driver Version

8.0.3.0.0

Yes, DB2 Driver Yes, DB2 Driver Yes, DB2 Driver Yes, DB2

Driver

Yes, Microsoft SQL Driver

Yes, Or ac le Driver Version

2.0.3.1.1

No Yes, Oracle

Yes, Microsoft SQL Driver

Yes, Or ac le Driver Version

2.0.3.1.1

Driver Version

8.0.3.0.0

Yes, Visigenic Driver Version 1.10

No No

Sybase SQL Version

11. 0

Note: The above applies to Netfinity Manager Release 5.2.0 and later.

Yes, Sybase Driver Version

10.0.3T4

Yes, Sybase Driver Version

10.0.3T4

Yes, Sybase Driver Version

10.0.3T4

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

No No

92 Hardware Maintenance Manual: Netfinity 4500R Type 8656

IBM Netfinity 4500R Type 8656, 8656 Hardware Maintenance Manual

Specifications and Main Features

Frequently Asked Questions

User Manual