IBM NETFINITY 5000 (TYPE 8659) NETFINITY 5000 (TYPE 8659) User Manual

Download

IBM Netfinity Servers

IBM Netfinity 5000 - Type 8659 Models 12Y, 1SY, 22Y, 2SY, 31Y, 3RY, 41Y, 4RY,

51Y, 5RY, 61Y, 6RY, 71Y, 7RY, 81Y, 8RY

Hardware Maintenance Manual

January 2000

We Want Your Comments! (Please see page 206)

S10L-9837-04

IBM Netfinity Servers

IBM Netfinity 5000 - Type 8659 Models 12Y, 1SY, 22Y, 2SY, 31Y, 3RY, 41Y, 4RY,

51Y, 5RY, 61Y, 6RY, 71Y, 7RY, 81Y, 8RY

Hardware Maintenance Manual

January 2000

We Want Your Comments! (Please see page 206)

S10L-9837-04

IBM

Note

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

Fifth Edition (January 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.

Note to U.S. Government users–Documentation related to Restricted rights–Use, duplication, or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

ii Netfinity Server HMM

About this manual

This manual contains diagnostic information, Symptom-to-FRU Indexes, service information, error codes, error messages, and configuration information for the Netfinity 5000 - Type 8659.

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.

iii

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) or the IBM BBS to download Diagnostic, BIOS Flash, and Device Driver files.

File download address is:

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

The IBM BBS can be reached at (919) 517-0001.

IBM online addresses:

The IBM Support Page is:

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

The IBM Home Page is:

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

iv Netfinity Server HMM

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

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

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

Netfinity 5000 - Type 8659 ............ 1

General Checkout . . . . . . . . . . . . . . . . . 5

Diagnostic tools . . . . . . . . . . . . . . . . . . 8

Features . . . . . . . . . . . . . . . . . . . . . 14

Additional service information ........... 16

Locations . . . . . . . . . . . . . . . . . . . . . 55

Symptom-to-FRU index . . . . . . . . . . . . . 152

Undetermined problems . . . . . . . . . . . . . 165

Parts listing (Type 8659) ............ 167

Related service information .......... 175

Safety information . . . . . . . . . . . . . . . . 176

Send us your comments! ............ 206

Problem determination tips ........... 207

Phone numbers, U.S. and Canada ........ 208

Trademarks . . . . . . . . . . . . . . . . . . 210

 Copyright IBM Corp. 2000 v

vi Netfinity Server HMM

Netfinity 5000 - Type 8659

General Checkout . . . . . . . . . . . . . . . . . 5

Diagnostic tools . . . . . . . . . . . . . . . . . . 8

Diagnostic tools overview ........... 8

Diagnostic LEDs . . . . . . . . . . . . . . 8

Diagnostic test programs .......... 8

Power-on self-test (POST) ......... 9

POST beep codes ............. 10

Error messages . . . . . . . . . . . . . . 10

POST error messages and beep codes . . 10

Diagnostic error messages ........ 10

Software-generated error messages . . . 10

Option diskettes . . . . . . . . . . . . . . 10

Diagnostic test programs ............ 10

Navigating through the diagnostic tests . . . 11

Running Diagnostic test programs ...... 12

Viewing the test log ............. 13

Features . . . . . . . . . . . . . . . . . . . . . 14

Additional service information ........... 16

Checking the system for damage ........ 17

After dropping it .............. 17

After spilling liquid on it ........... 17

Configuration overview . . . . . . . . . . . . . 18

Configuration/Setup utility . . . . . . . . . . . 20

Configuration/Setup utility usage ........ 22

System summary . . . . . . . . . . . . . . 22

System information . . . . . . . . . . . . . 23

Product data . . . . . . . . . . . . . . 23

System card data ............ 23

PCI routing . . . . . . . . . . . . . . . . . 23

Devices and I/O ports ............ 23

Date and time ............... 24

System security . . . . . . . . . . . . . . 24

Using the power-on password menu . . . 26

Using the administrator password menu . 27

Defining a system owner's name ..... 28

Start options . . . . . . . . . . . . . . . . 29

Advanced setup . . . . . . . . . . . . . . 29

Core chipset control ........... 29

PCI bus control ............. 30

Cache control . . . . . . . . . . . . . . 30

Memory settings . . . . . . . . . . . . . 30

Advanced ISA settings .......... 30

Service Processor IRQ settings ..... 30

Plug and Play ............... 31

Error log . . . . . . . . . . . . . . . . . . 31

Configuring PCI features and options .... 31

Configuring the Ethernet controller ....... 32

Ethernet controller messages .......... 34

Novell NetWare or IntraNetWare Server ODI

driver messages . . . . . . . . . . . . . 34

NDIS 2.01 (OS/2) driver messages ..... 36

 Copyright IBM Corp. 2000 1

NDIS 4.0 (Windows NT) driver messages . . 38

UNIX messages . . . . . . . . . . . . . . 38

Failover for redundant Ethernet ......... 41

Configuring Failover on OS/2 ........ 41

Configuring Failover on Windows NT .... 42

Configuring Failover on IntraNetWare .... 42

Identifying problems using status LEDs ..... 44

Power supply LEDs ............. 44

LED diagnostics . . . . . . . . . . . . . . 45

Recovering BIOS . . . . . . . . . . . . . . . 48

Resolving configuration conflicts ........ 49

Resolving memory-address conflicts ..... 49

Changing the software configuration setup . . 49

Changing the hardware configuration setup . 49

Resolving resource conflicts .......... 50

Resolving hardware configuration conflicts . . 50

Resolving software configuration conflicts . . 51

Using the SCSISelect utility program ...... 52

Starting the SCSISelect utility program .... 52

SCSISelect utility program choices ...... 52

Configure/View host adapter settings . . . 52

SCSI disk utilities ............ 53

Performing a low-level disk format .... 54

When to use the format disk program . . . 54

Starting the low-level format ....... 54

Verifying the disk media ......... 54

Locations . . . . . . . . . . . . . . . . . . . . . 55

Adapters . . . . . . . . . . . . . . . . . . . 56

Adapter considerations . . . . . . . . . . . 56

Installing or removing adapters ....... 57

Battery . . . . . . . . . . . . . . . . . . . . 61

Bays . . . . . . . . . . . . . . . . . . . . . 64

Types of cables .............. 65

SCSI devices . . . . . . . . . . . . . . . . 66

SCSI IDs . . . . . . . . . . . . . . . . 66

Termination requirements . . . . . . . . 67

Preinstallation steps (all bays) ........ 67

Installing or removing drives in bays A and B

(removable media) . . . . . . . . . . . . 69

Installing or removing a drive in bay C (diskette

drive) . . . . . . . . . . . . . . . . . . . 70

Installing or removing drives in bays 1 through 5

(hard disk drives) ............. 72

Changing jumper positions ........... 75

Two-pin jumper blocks ........... 75

Completing the installation ........... 77

Completing the tower model installation ..... 77

Completing the rack model installation .... 80

Controls . . . . . . . . . . . . . . . . . . . . 82

Front panel indicators ............ 85

DASD fan assembly removal .......... 90

Ethernet connector . . . . . . . . . . . . . . . 91

Expansion bays . . . . . . . . . . . . . . . . 92

External options . . . . . . . . . . . . . . . . 94

2 Netfinity Server HMM

Adding External SCSI devices ........ 94

Attaching external options .......... 95

Hot-swap backplane assembly removal ..... 96

Input/Output connectors . . . . . . . . . . . . 97

Installing a server in a rack enclosure ...... 99

Before you begin ............. 100

Installing the rack model in a rack enclosure 102

Preparing the server .......... 102

Preparing the rack enclosure ...... 104

Installing the server in the rack enclosure 108

Removing the rack model from a rack

enclosure . . . . . . . . . . . . . . . . 111

Internal drives installation or removing .... 113

Keyboard and mouse connectors ....... 114

Management port C ............. 115

Memory modules . . . . . . . . . . . . . . 116

Installing or removing memory modules . . 116

Microprocessors . . . . . . . . . . . . . . . 118

Installing microprocessor upgrades .... 118

Installing or replacing a microprocessor . . 119

Option installation . . . . . . . . . . . . . . 125

Preparing a tower model ......... 126

Preparing a rack model .......... 128

Parallel port connector ............ 131

Power supplies . . . . . . . . . . . . . . . 132

Power supply removal ............ 133

Rear fan assembly removal ......... 134

SCSI connectors . . . . . . . . . . . . . . . 135

Internal SCSI connector .......... 135

External SCSI connector ......... 135

SCSI jumpers . . . . . . . . . . . . . . . . 137

DASD backplane jumper block location . 138

Security . . . . . . . . . . . . . . . . . . . 139

Installing a U-bolt and security cable .... 139

Serial port connectors ............ 141

System board illustration ........... 142

System board LEDs ........... 142

System board connectors ......... 143

System board removal/replacement ...... 145

System board switches ............ 147

Bypassing an unknown power-on password 148

Universal serial bus ports .......... 149

Updating the server configuration ....... 150

Video port connector ............. 151

Symptom-to-FRU index . . . . . . . . . . . . . 152

Beep symptoms . . . . . . . . . . . . . . . 152

No beep symptoms ............. 155

Diagnostic error codes ............ 156

Error symptoms . . . . . . . . . . . . . . . 159

POST error codes .............. 160

SCSI error codes .............. 165

Undetermined problems . . . . . . . . . . . . . 165

Parts listing (Type 8659) ............ 167

System . . . . . . . . . . . . . . . . . . . 168

Netfinity 5000 - Type 8659 3

Keyboards . . . . . . . . . . . . . . . . . 172

Power cords . . . . . . . . . . . . . . . . . 174

4 Netfinity Server HMM

General Checkout

The server diagnostic programs are stored in nonvolatile random-access memory (NVRAM) 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 port, and parallel port. You can also use them to test some external devices.

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.

Netfinity 5000 - Type 8659

Notes

1. For systems that are part of a shared DASD cluster, run one test at a time in looped mode. Do not run all tests in looped mode, as this could enable the DASD diagnostic tests.

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

3. If the computer hangs with a POST error, go to the “Symptom-to-FRU index” on page 152.

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

5. Power Supply problems, see “No beep symptoms” on page 155.

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

7. For intermittent problems, check the error log; see, “Error log” on page 31.

001

IS THE SYSTEM PART OF A CLUSTER? Yes No

002

Go to Step 004.

(CONTINUED)

003

Schedule maintenance with the customer. Shut down all systems related to the cluster. Run storage test.

004

– 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. – Check the error log, see “Error log” on page 31. If an

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

– Start the Diagnostic Programs. See “Running

Diagnostic test programs” on page 12.

– Check for the following responses:

1. No beep.

2. Readable instructions or the Main Menu.

DID YOU RECEIVE THE CORRECT RESPONSES? Yes No

005

Find the failure symptom in “Symptom-to-FRU index” on page 152.

6 Netfinity Server HMM

006

– Run the Diagnostic Programs. If necessary, refer to

“Running Diagnostic test programs” on page 12. If you receive an error, go to “Symptom-to-FRU index” on page 152. If the diagnostics completed successfully and you still suspect a problem, see “Undetermined problems” on page 165.

Netfinity 5000 - Type 8659 7

Diagnostic tools

Server problems can be caused by the hardware, the software, or a user error. An example of a user error is pressing the wrong key on the keyboard.

You can check the hardware by using the diagnostic test programs and the information in this section.

Note

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

If the hardware is OK and you have not made an error, you might have a software problem. If you suspect that you have a software problem, refer to the information that comes with that software package.

Diagnostic tools overview

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

 LEDs on the system board and power supplies  Diagnostic test programs  Power-on self-test (POST)  POST beep codes

 Error messages  Troubleshooting charts  Option diskettes

Diagnostic LEDs: When a system error occurs, the

relevant LEDs on the system board are lighted to identify where the errors are (see “System board LEDs” on page 142). When you see the System Error LED illuminated on the operator LED (status) panel on the front of the server, check the LEDs on the power supplies and at any Ethernet adapters, then open the cover and see which LEDs are illuminated on the system board.

Diagnostic test programs: The server

diagnostics test programs are stored in nonvolatile random-access memory (NVRAM) on the system board. These programs are the primary method of testing the system board, memory, and other standard features of the Netfinity 5000. You can also use them to test some external devices.

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

8 Netfinity Server HMM

The server diagnostic test programs can identify most problems associated with major components of the server: the system board, Ethernet controller, video controller, RAM, diskette drive, serial port, parallel port, keyboard, and mouse.

You can start the diagnostic test programs from the Startup panel, when the message Press F2 for Diagnostics appears. Test options let you batch groups of tests, specify test parameters (for example, which memory DIMM you want to test), and specify the number of passes that you want to run (1 through 9999).

You can also view the server configuration information from the Diagnostic Utility menu. For example, you can view the interrupt request (IRQ) and direct memory access (DMA) assignments, memory usage, device drivers, and so on.

Power-on self-test (POST): When you turn on

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

POST does the following:

 Checks the operation of some basic system board

operations

 Checks the memory  Compares the current server configuration with the

stored server configuration information

 Configures PCI adapters  Starts the video operation  Verifies that drives (such as the diskette, CD-ROM,

and hard disk drives) are connected properly

If you have a power-on password or administrator password set, you must type the password and press Enter before POST will continue.

While the memory is being tested, the amount of available memory appears on the screen. These numbers advance as the system progresses through POST and the final number that appears on the screen represents the amount of memory available. If POST finishes without detecting any problems, a single beep sounds, the POST OK on the front LED panel comes on, and the first screen of the operating system or application program appears.

If POST detects a problem, an error message appears on the screen. A single problem can cause several error messages to appear. When this occurs, work to correct the cause of the first error message. After the cause is corrected, the other error messages probably will not appear the next time you turn on the system.

Netfinity 5000 - Type 8659

POST beep codes: POST generates beep codes to

indicate successful completion or the detection of an error.

 One beep indicates successful completion of POST.  More than one beep indicates that POST detected an

error, see “Beep symptoms” on page 152

Error messages: Error messages indicate that a

problem exists; they are not intended to be used to identify a failing part.

Hardware error messages that occur can be text, numeric, or both. Messages generated by the software generally are text messages, but they also can be numeric.

POST error messages and beep codes:

error messages and beep codes occur during startup when POST finds a problem with the hardware or detects a change in the hardware configuration, see “Symptom-to-FRU index” on page 152.

Diagnostic error messages:

messages occur when a test finds a problem with the server hardware. These error messages are alphanumeric and they are saved in the Test Log.

Diagnostic error

Software-generated error messages:

messages occur if a problem or conflict is found by an application program, the operating system, or both. Messages are generally text messages, but they also can be numeric. For information about these error messages, refer to the documentation that comes with the software.

POST

These

Option diskettes: An optional device or adapter

might come with an Option Diskette. Option Diskettes usually contain option-specific diagnostic test programs or configuration files.

If the optional device or adapter comes with an Option Diskette, follow the instructions that come with the option. Different instructions apply depending on whether the Option Diskette is startable or not.

Diagnostic test programs

This section includes useful information about navigating through the diagnostic test programs, as well as procedures for starting and stopping them. These programs are designed to test the IBM Netfinity 5000. If you want to test a non-IBM product, refer to the information that comes with that product.

You can start the diagnostic test programs from the Startup panel, when the message Press F2 for Diagnostics appears.

10 Netfinity Server HMM

Note

Navigating through the diagnostic tests:

Error messages in the Test Log are stored by diagnostic test session. A diagnostic test session is defined as running one, all, or a selection of tests, one or more times. You can use the following keys to maneuver within the test program:

Enter Selects an item. Down Arrow (↓) Moves the cursor down. Up Arrow (↑) Moves the cursor up. Left Arrow (←) Toggles test selection between

Yes and No.

Right Arrow (→) Toggles test selection between

Yes and No.

Page Down (PgDn) Moves to the next diagnostic

test session in the log (if any).

Page Up (PgUp) Moves to the previous

diagnostic test session in the log (if any).

F1 Displays the appropriate Help

information. Use the Up Arrow (↑) or Down Arrow (↓) key to scroll through the information. Pressing F1 from within a Help screen provides a help index from which you can select different categories. Pressing Esc exits Help and returns to where you left off.

Esc Returns to the previous menu.

Netfinity 5000 - Type 8659

Running Diagnostic test programs: When

you start the diagnostic test programs from the Diagnostic Utility menu, you can select the tests, the way the tests run, and the number of times the tests run.

Notes

1. To run the diagnostic test programs, you must start the server with the highest level password.

That is, if you enter the power-on password, and an administrator password is set, you cannot run the test programs. You can only view the error messages in the test log.

If an administrator password is set, you must enter the administrator password to run the diagnostic test programs.

2. If the server stops during testing and you cannot continue, restart the server and try running the tests again. If the problem persists, see “Error symptoms” on page 159 and look for the problem symptom.

3. If the diagnostic tests do not find a problem, see “Error symptoms” on page 159 and look for the problem symptom.

4. You might need a scratch diskette to obtain accurate test results when testing the diskette drive.

5. The keyboard and mouse tests assume that a keyboard and mouse are attached to the server.

To start the diagnostic tests:

1. Turn on the server and watch the screen. If the system is turned on already, shut down the

operating system and restart the server.

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

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

3. The Diagnostic Programs screen appears.

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

5. Select the test you want to run from the list that appears; then, follow the instructions that appear on the screen. The actions available include specifying the options for the tests to be run, such as the number of times to run the test, whether to stop on error, or whether to use a predefined overlay that describes the tests to be run.

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

12 Netfinity Server HMM

Also, you can view server configuration information (such as system configuration, memory contents, interrupt request (IRQ) use, direct memory access (DMA) use, device drivers, and so on) by selecting Hardware Info from the top of the screen.

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

Viewing the test log: If you are already running

the diagnostic programs, continue with step 4 in this procedure.

To view the Test Log:

1. Turn on the server and watch the screen. If the system is turned on already, shut down the

operating system and restart the server.

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

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

3. The Diagnostic Programs screen appears. After you run diagnostic tests or abort the diagnostic tests, the utility option appears at the top of the screen.

4. Select Utility from the top of the screen.

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

6. Press Esc to return to the Diagnostic Programs screen.

7. Select Quit from the top of the screen; then, select Exit Diags to exit from the diagnostic programs. The server restarts.

Netfinity 5000 - Type 8659

Features

The following table summarizes the features of the Netfinity 5000 - Type 8659.

Microprocessor

 Intel Pentium II microprocessor

with MMX technology

 512 KB of level-2 cache (min)

Memory

 Standard: 64 MB (min), expandable to 1 GB  100 MHz, error correcting code (ECC) registered

synchronous dynamic random access memory (SDRAM)

 Four dual-inline memory-module (DIMM) sockets

Diskette Drive

 One 3.5-inch, 1.44 MB

Hard Disk Drives

 Up to five hot-swappable internal hard disk drives are

supported

CD-ROM Drive

 Standard: IDE Keyboard and Auxiliary Device (tower models)

 Keyboard  Mouse

Expansion Slots

Supports up to five adapters

 One ISA slot  Two shared PCI/ISA slot  Three dedicated PCI slots

Expansion Bays

 One 3.5-inch diskette drive bay  Two 5.25-inch drive bays, open bay supports

half-high SCSI tape drive

 Five 3.5-inch drive bays, hot-swappable

Upgradable Microcode

 BIOS, diagnostics, and Netfinity Advanced System

Management Processor code upgrades (when available) can update EEPROMs on the system board

Power Supply

 350W with voltage auto-selection (110, 120, 220,

240 V ac) and power redundancy

– Standard—350W non-redundant, 175 W

redundant

14 Netfinity Server HMM

– Optional—Additional 175W power supply

available for 350W redundancy

 Built-in overload and surge protection  Automatic restart after a momentary loss of power

Integrated Functions

 Two serial ports  Two universal serial bus (USB) ports  System management port (C)  Advanced system management processor on system

board

 One IDE internal connector, supports the system IDE

CD-ROM drive

 One parallel port  Mouse port  Keyboard port

 16-bit UltraSCSI controller

– One external connector (16-bit) – One internal connector (16-bit)

 Full-duplex 10/100 Mbps Ethernet controller

– 10BASE-T/100BASE-TX port

– Redundant Ethernet capability, through the use

of an optional network interface card (NIC)

 Video controller port, super video graphics array

(SVGA)

 1 MB video memory

Security Features

 Bolt-down capability

 Door lock (tower model only)

 Power-on and administrator passwords

 Selectable startup sequence

Netfinity 5000 - Type 8659 15

Additional service information

The following additional service information supports Netfinity 5000 - Type 8659.

 “Checking the system for damage” on page 17.  “Configuration overview” on page 18.  “Configuration/Setup utility” on page 20.  “Configuration/Setup utility usage” on page 22.  “Configuring the Ethernet controller” on page 32.  “Ethernet controller messages” on page 34.  “Failover for redundant Ethernet” on page 41.  “Identifying problems using status LEDs” on page 44.  “Recovering BIOS” on page 48.  “Resolving configuration conflicts” on page 49.  “Resolving resource conflicts” on page 50.

16 Netfinity Server HMM

Checking the system for damage

This section provides instructions on what to do if the system might be damaged.

After dropping it: Look for loose cables and

obvious damage. If any cables are loose, reconnect them securely.

If you see no damage, turn on the system. If it works correctly, the system probably did not suffer any damage.

If the system does not work correctly, turn it off and check the adapters and memory modules to ensure that they are connected correctly. Reseat all adapters and memory modules.

If the system still does not work correctly, run the diagnostic tests from diagnostic utility menu. For information about running tests, see “Running Diagnostic test programs” on page 12.

After spilling liquid on it: If liquid gets on the

keyboard:

1. Turn off the server.

2. Unplug the keyboard from the back of the server.

3. Turn the keyboard upside down to drain excess liquid.

4. Dry off the keyboard with a lint-free cloth.

After the keyboard is completely dry, plug it in and turn on the server. If it does not work correctly, replace the keyboard.

If liquid gets inside the monitor:

1. Turn off the monitor.

2. Turn off the server.

3. Unplug the monitor from the server and the electrical outlet.

4. Let the monitor dry out.

If liquid gets inside the server:

1. Turn off the server and all attached devices.

2. Unplug the server from the electrical outlet and all attached devices.

3. Let the server dry out.

Netfinity 5000 - Type 8659

Configuration overview

You play a key role in how the server allocates resources to organize and interconnect hardware devices and software programs. This allocation process is referred to as

configuration

server depend on the number and types of devices and programs that you install.

The server supports several types of adapters. Because of this flexibility, you can choose from among thousands of adapters and devices that comply with any of the following standards:

 Peripheral Component Interconnect (PCI)  Industry Standard Architecture (ISA)  Small Computer System Interface (SCSI)

In general, the greater the number and variety of hardware devices and software programs that you install in the server, the more you will have to interact with the server and the devices to correctly configure the system.

The server comes with the following hardware configuration utility programs:

 Configuration/Setup Utility

With the built-in Configuration/Setup Utility program, you can configure system board functions, such as serial and parallel port assignments; change interrupt request settings; and change the startup sequence for drives that you install. You can also use this utility program to set passwords for starting up the server and accessing the Configuration/Setup Utility program.

 SCSISelect Utility

With the built-in SCSISelect Utility program, you can configure the SCSI devices that you install in the server. You can use SCSISelect to change default values, resolve configuration conflicts, and perform a low-level format on a SCSI hard disk drive.

Before installing a new device or program, read the documentation that comes with it. Reading the instructions helps you determine the steps required for installation and configuration. The following actions are typically, but not always, required to configure the server.

. The steps required to configure the

18 Netfinity Server HMM

1. Run the Configuration/Setup Utility program and record the current configuration settings.

2. Set switches on the server system board. See “System board switches” on page 147 for the

meanings of the system board switches.

3. Set jumpers or switches on the device. See the device installation instructions.

4. Install the device in the server, see “Locations” on page 55.

5. Install software programs. Refer to the information provided with the

“ServerGuide and Netfinity Manager Information” section of this

Server Library

and with the operating

system for more information.

6. Resolve configuration conflicts. See “Resolving resource conflicts” on page 50.

Netfinity 5000 - Type 8659

Configuration/Setup utility

For most configurations, the server will operate using the default system settings. You need to change the settings only to resolve configuration conflicts or to enable or change device functions.

When you want or need to change the default settings, the Configuration/Setup Utility program provides a convenient way to display and change the settings.

After you run and exit the Configuration/Setup Utility program, configuration information is stored in nonvolatile random-access memory (NVRAM). While the server is powered off, the configuration information remains available for the next system startup.

Always run the Configuration/Setup Utility program if you add or remove any hardware option, or if you receive an error message instructing you to do so. Review this chapter and the information that comes with the option before making changes. Also, record the current settings before making any changes.

To start the Configuration/Setup Utility program:

1. Turn on the server and watch the screen.

2. When the messages Press F1 for Configuration/Setup and Press F2 for Diagnostics appear, select the action you need.

 To configure the server, press F1 to select

Configuration/Setup Utility.

The Configuration/Setup Utility main menu appears. For information about the menus, see “Configuration/Setup utility usage” on page 22.

Note

If you enter a power-on password and an administrator password has been set, a limited menu appears on the screen. To access the full Configuration/Setup Utility menu, you must enter the administrator password.

 To run the system diagnostics, press F2 to

select Diagnostic Utility. The Diagnostic Utility main menu appears. For

information about running the system diagnostics, see “Diagnostic test programs” on page 10.

20 Netfinity Server HMM

Important

If a defective PCI adapter is causing the system to stop responding during startup, you can press Alt+F1 here. This will cause the server to bypass PCI device initialization (except video) and go directly to the Configuration/Setup Utility, where you can disable the defective PCI adapter. Disabling the defective PCI adapter should enable you to complete a normal startup when you restart the server.

Netfinity 5000 - Type 8659 21

Configuration/Setup utility usage

From the Configuration/Setup Utility program main menu you can select settings you want to change.

Pressing F1 displays Help information for a selected menu item.

Notes

1. If you enter only the power-on password and an administrator (supervisor-level) password is also set, a limited version of the menu appears. To view the full Configuration/Setup Utility menu you must enter the administrator password.

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

To change configuration settings:

1. Use the Up Arrow (↑) key to select the item you want to change; then, press Enter.

2. Select the configuration setting you want to change. Use the Right Arrow (→) or Left Arrow (←) key to highlight the menu, if needed.

3. Use the Right Arrow (→) or Left Arrow (←) key to select the appropriate setting for the selected item.

4. Repeat Steps 1 through 3 for each setting that you want to change. Press Esc to return to the Configuration/Setup Utility main menu.

5. After making changes, you can select:

 Save Settings to save the selected changes.  Restore Settings to delete the selected

changes.

 Load Default Settings to cancel the changes

and restore the factory settings.

6. To exit from the Configuration/Setup Utility main menu, select Exit Setup.

7. The system prompts you to confirm your choice. You can return to the Configuration/Setup Utility main menu, or exit.

System summary: Select this choice to display

configuration information, such as the type and speed of the microprocessor, and amount of memory.

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

22 Netfinity Server HMM

System information: Select this choice to display

information about the Netfinity 5000, Changes that you make on other menus might appear on

this summary screen.

Product data:

information such as the machine type and model, the system serial number, the system board identifier, and the revision level or issue date of the flash electronically erasable programmable ROM (EEPROM) and BIOS.

System card data:

system board model, submodel, system serial number, system board identifier, DASD backplane identifier, and identifiers for power supply 1 and power supply 2.

Select this choice to view system

Select this choice to view the

PCI routing:

Select this choice to view the interrupt request (IRQ) settings for PCI adapters and for the Ethernet, SCSI, and other controllers on the system board. See “PCI bus control” on page 30 for information about changing the PCI IRQ settings.

Devices and I/O ports: Software recognizes ports

from their port assignments. Each port must have a unique port assignment. The Configuration/Setup Utility program normally handles this, but you might have special hardware or software that requires you to change these assignments.

Note

Serial port A can be shared by the system management processor and operating system. Serial port B is used by the operating system only. Management port C is controlled exclusively by the system management processor, cannot be used by the operating system, and cannot be configured using the Configuration/Setup Utility program. See the “Advanced System Management Information” section of this

Server Library

serial ports A and C.

for information about configuring

Select the Devices and I/O Ports choice to view or change the assignments for devices and input/output ports.

Netfinity 5000 - Type 8659 23

You can add serial ports by installing a serial adapter in an expansion slot. See the documentation that comes with the serial adapter for information about port assignments.

You can configure the parallel port as standard, as bidirectional, as an Extended Capabilities Port (ECP), or as an Enhanced Parallel Port (EPP). Bidirectional, ECP, and EPP are all bidirectional modes; in all three modes, data can be both read from and written to a device. ECP and EPP are industry-standard, high-performance bidirectional modes. Which one of these modes you choose depends on what mode the device supports.

Note

When you configure the parallel port as bidirectional, ECP, or EPP, use an IEEE 1284-compliant cable. The maximum length of the cable must not exceed 3 meters (9.8 feet).

You can configure the mouse and diskette controller as enabled or disabled, and configure the type of diskette drive.

You can view the type of video controller and the amount of video memory installed.

You can configure the IDE channel (enabled or disabled) and view the IDE Primary Master Device (type, size, transfer selection and mode, and logical block addressing (LBA) mode).

To display or change the port assignments:

1. Select Devices and I/O Ports.

2. Select a device or port; then, use the Left Arrow (←) or Right Arrow (→) key to advance through the settings available.

Date and time: Select this choice to set the system

date and time. The system time is in a 24-hour format:

hour/minute/second. The system date is in standard format for your country. For example, in the United States, the format is MM/DD/YYYY (Month/Day/Year).

Select Date and Time; then, use the Left Arrow (←) or Right Arrow (→) key to advance through each data field. Type the new information; the system saves the information as you type it.

System security: To control access to the

information in the server, you can implement security features, such as adding passwords and defining a system owner's name that displays during startup. Implementing these security measures helps you to ensure the integrity of the data and programs that are stored in the server.

24 Netfinity Server HMM

After setting a power-on password, you can enable the unattended-start mode. This locks the keyboard and mouse, but allows the server to start the operating system. The keyboard and mouse remain locked until you enter the correct password.

To set, change, or delete a password:

1. Select System Security.

2. Select the password that you want to change.

3. Follow the instructions on the screen.

After you have set a power-on or administrator password, you must enter the password whenever you turn on the server. (The passwords do not appear on the screen as you type them.)

Type of Password Results

No password set  No password required to start system.

Power-on password only

Administrator password only

Administrator power-on password

and

 You can access all choices on the

Configuration/Setup Utility program main menu.

 You must enter the password to complete

the system startup.

 You can access all choices on the

Configuration/Setup Utility program main menu.

 If you forget the power-on password, you

can regain access to the server by using switch 8 on the system board. See “Using the power-on password menu” on page 26 for details.

 You must enter the password to enter the

Configuration/Setup Utility program.

 You can access all choices on the

Configuration/Setup Utility program main menu.

 If the administrator password is forgotten, it

cannot be overridden or removed. You must replace the system board.

 You can enter either password to complete

the system startup.

– Administrator password provides

access to all choices on the Configuration/Setup Utility program 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.

– Power-on password provides access to

a limited set of choices on the Configuration/Setup Utility program main menu. This might include changing or deleting the power-on password.

 If you forget the power-on password, and

the administrator password has been set, use the administrator password at the password prompt. Then, start the Configuration/Setup Utility program and change the power-on password.

Netfinity 5000 - Type 8659 25

Using the power-on password menu:

power-on password is set, you must enter a password each time you start the system.

To set a power-on password:

1. Select Power-on Password from the System Security menu; then, press Enter.

The Power-on Password menu appears.

2. Type the password in the Enter Power-on Password data field.

You can use any combination of up to seven characters (A–Z, a–z, and 0–9) for the power-on password. Keep a record of the password in a secure place.

3. Move the cursor to the Enter Power-on Password

Again data field and type the password again.

Note

A message appears if the two passwords do not match. If this happens, press Enter to return to the Power-On Password menu.

4. Select Change Power-on Password to save the new password; then, press Enter.

5. A confirmation window appears. Press Enter to change the power-on password. Press Esc to return to the System Security menu.

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

 If an administrator password has been set, enter the

administrator password at the power-on prompt (see “Using the administrator password menu” on page 27 for details). Start the Configuration/Setup Utility program and change the power-on password as described in steps 1 through 5 above.

 Use the Bypass-Power-On-Password switch on the

system board to temporarily bypass the power-on password.

1. See “Option installation” on page 125 through “Preparing a tower model” on page 126 or through “Preparing a rack model” on page 128 for instructions on powering off the server and removing the cover. Then, refer to the system board diagram inside the server for the location of the switch block.

2. Locate switch 8 (see “System board switches” on page 147).

3. Set switch 8 on the switch block to On, to bypass the power-on password.

4. Restart the server, then start the Configuration/Setup Utility program and change

When a

26 Netfinity Server HMM

the power-on password as described in steps 1 through 5 above.

5. Turn the server off again.

6. Set switch 8 back to Off.

7. Restart the server.

To delete a power-on password:

1. Select Power-on Password from the System Security menu; then, press Enter.

The Power-on Password menu appears.

2. Select Delete Power-on Password; then, press

Enter.

3. A confirmation window appears. Press Enter to delete the power-on password. Press Esc to cancel the request and return to the System Security menu.

To allow the server to start in unattended mode when a power-on password is set:

Note

If the password data field is set to On, the Unattended Start and Stop modes are not

supported.

1. Select Power-on Password from the System Security menu; then, press Enter.

The Power-on Password menu appears.

2. Select Allow for unattended boot with password. Press the Left Arrow (←) or Right Arrow (→) key to toggle the entry to On.

If no power-on password is set on the server, this option has no effect.

Using the administrator password menu:

administrator password (sometimes called a supervisor-level password) controls access to some features of the server, including the Configuration/Setup Utility program.

Important

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

To set an administrator password:

1. Select Administrator Password from the System Security menu; then, press Enter.

2. Type the password in the Enter Administrator Password data field.

A password can contain any combination of up to seven alphanumeric characters (A–Z, a–z, and 0–9). Keep a record of the password in a secure place.

Netfinity 5000 - Type 8659

The

3. Move the cursor to the Enter Administrator Password Again data field and type the password

again.

Note

A message appears if the two passwords do not match. If this happens, press Enter to return to the Administrator Password menu.

4. Select Change Administrator Password to save the new password; then, press Enter. The password becomes effective immediately.

To delete an administrator password:

1. Select Administrator Password from the System Security menu; then, press Enter.

2. Select Delete Administrator Password; then, press Enter.

3. A confirmation window appears. Press Enter to delete the administrator password. Press Esc to return to the System Security menu.

To enable a user to change the power-on password:

1. Select Administrator Password from the System Security menu; then, press Enter.

2. Select Power-on password changeable by user. Press the Left Arrow (←) or Right Arrow (→) key to toggle the entry to Yes.

When this choice is enabled, System Security appears on the limited Configuration/Setup menu. The System Security menu contains the Power-on Password choice.

Defining a system owner's name:

a system owner's name that displays during POST each time that the server is started. If you set an administrator password, only the administrator can set, change, or delete the system owner's name.

To set the system owner's name:

1. Select System Owners Name from the System Security menu; then, press Enter.

The System Owners Name screen appears.

2. Type the name in the Enter System Owners Name String data field. You can use any combination of up to 15 characters and spaces in the system owner's name.

3. Press the Down Arrow (↓) key to select the Set or Change System Owners Name data field.

4. Press Enter to set the name or change a previously defined name.

To delete the system owner's name, select Delete Stored System Owners Name; then, press Enter.

You can specify

28 Netfinity Server HMM

Start options: Start options take effect when you

start the server. You can select keyboard operating characteristics, such as

the keyboard speed. You also can specify whether the keyboard number lock (NumLock) starts on or off. You also can enable the server to run in disketteless and monitorless operation.

You can specify the startup sequence the server is to use to determine the device from which the operating system loads. For example, you can define a startup sequence that checks for a CD-ROM, then checks an installed hard disk drive, and then checks a network adapter.

Attention: If the CD-ROM drive contains a startable CD, you must remove the CD if you want to use a startup sequence that begins with a startable diskette.

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

Select Start Options; then, use the Left Arrow (←) or Right Arrow (→) key to advance through each data field.

Advanced setup: Select Advanced Setup to

change values for advanced hardware features, such as cache control, PCI bus control, memory settings, and advanced ISA settings.

Note

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

Use the Left Arrow (←) or Right Arrow (→) key to highlight the options for the selected menu item.

Core chipset control:

settings that control features of the core chip set on the system board. The chipset control choices are:

IOQ Depth Use this setting to control the in order queue

(IOQ) depth in the system. The value can be varied from 1 to 8. This value should normally be set at 8 (default)

Grant Timers Use this setting to enable or disable the

grant timer mechanism for each of the 5 PCI slots. Enabling this will cause grant to be asserted to a PCI bus agent for a minimum of two clocks. This setting should normally be set to disable (default)

Netfinity 5000 - Type 8659

Select this choice to modify

PCI bus control

Note

This page shows the interrupts and the correct interrupt assigned to the devices.

Select PCI Bus Control to:

 Change the master latency timer values for PCI bus 1

and PCI bus 2.

 Specify the system board interrupt routing (IRQs) for

SCSI, Ethernet, video, and USB.

 Specify the slot interrupt routing (IRQs) for PCI slots.  Enable and disable PCI device types (SCSI, video,

Ethernet) and slots. When a PCI adapter is defective, you can use Alt+F1 at startup and then disable the PCI adapter in order to enable the system to start up successfully.

Note

Any changes you make to IRQs will not be reflected in the PCI Interrupt Routing selection of this menu until you restart the server.

Cache control:

microprocessor cache state as enabled or disabled, and to define the microprocessor cache type as Write-back or Write-through.

Selecting write-back mode will provide the maximum system performance.

Memory settings:

banks of memory and to enable or disable selected rows of memory within those banks.

If a memory error is detected during POST or memory configuration, the server can automatically disable the failing row of memory and continue operating with reduced memory capacity. If this occurs, you must manually enable the row of memory after the problem is corrected. Choose Memory Settings from the Advanced Setup menu; then use the the Up Arrow (↑) or Down Arrow (↓) key to highlight the row that you want to enable. Use the Left Arrow (←) or Right Arrow (→) key to select Enable.

Advanced ISA settings:

timer delay for ISA I/O recovery.

Service Processor IRQ settings:

to specify the IRQ the system-management processor is to use and to synchronize the service processor clock to the system clock.

Select this choice to define the

Select this choice to view the server

Use this selection to set the

Use this selection

30 Netfinity Server HMM

Plug and Play: Most adapters designed for PCI slots

are Plug and Play devices that are auto-configuring. However, many ISA adapters are not Plug and Play devices and you must allocate the system resources that the adapter will use. Select Plug and Play to identify the available system resources:

 Memory  I/O ports  DMA  Interrupt

Note

The menus do not contain resources that are used by the system or by previously installed Plug and Play adapters.

Select Plug and Play; then, use the Up Arrow (↑) and Down Arrow (↓) key to highlight the system resource that you want to change. Use the Left Arrow (←) or Right Arrow (→) key to toggle from Plug and Play to ISA

Legacy for the selected menu choice.

Error log: Select Error Log to view the three most

recent power-on self-test (POST) errors the system has generated, or to view the system error log. You can clear both error logs from this screen by selecting Clear Error

Logs.

Configuring PCI features and options: PCI

devices automatically communicate with the server configuration information. This usually results in automatic configuration of a PCI device. If a conflict does occur, see “Resolving resource conflicts” on page 50.

Multiple-function PCI adapters use more than one interrupt. When you install one of these adapters, review the IRQ assignments in the Configuration/Setup utility programs (see “PCI bus control” on page 30). Verify that the IRQ assignments are correct.

The Netfinity 5000 server uses a rotational interrupt technique to configure PCI adapters. This technique enables you to install a variety of PCI adapters that currently do not support sharing of PCI interrupts. For information on manually overriding the interrupt setting, see “PCI bus control” on page 30.

Netfinity 5000 - Type 8659

Configuring the Ethernet controller

The Netfinity 5000 comes with an Ethernet controller on the system board. The Ethernet controller provides 10BASE-T and 100BASE-TX support through the RJ-45 connector on the back of the server.

When you connect the server to the network, the Ethernet controller automatically detects the data-transfer rate (10 Mbps or 100 Mbps) 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). This process is also known as

auto-negotiation

software intervention. The controller supports half-duplex (HDX) and full-duplex (FDX) modes at both speeds.

Auto-negotiation works only if the hub or switch to which the server is connected also supports auto-negotiation. If the hub or switch does not support auto-negotiation, the speed (10 Mbps or 100 Mbps) will still be detected correctly, but half-duplex mode will always be selected. A full-duplex switch that does not support auto-negotiation will not attach to the Netfinity 5000 in full-duplex mode.

In this case, if you want the network to operate in full-duplex mode, you must manually override the settings to obtain a full-duplex connection. To do this, the server must have a device driver that supports manual overrides. Use the ServerGuide CDs to install this device driver. Refer to the “ServerGuide and Netfinity Manager Information” section of this on installing device drivers. The ServerGuide CDs contain IBM Update Connector, a dial-up1 program that keeps the BIOS and device drivers current. Verify that you have installed the appropriate device driver. Also, refer to the Ethernet documentation for additional information on operating modes, manual overrides, and device drivers.

Attention:

 The 10BASE-T Ethernet and the 100BASE-TX Fast

Ethernet cabling in the network must be Category 5 or higher to meet various standards, including electromagnetic compatibility.

 You must install a device driver to enable the

operating system to address the Ethernet controller. Use the ServerGuide CDs to install this device driver. Refer to the information in the “ServerGuide and Netfinity Manager Information” section of this

. This auto-negotiation occurs without

Server Library

for instructions

Server

Response time will vary, depending on the number and nature of calls received.

32 Netfinity Server HMM

Library

for instructions on installing device drivers, or

for more information about the ServerGuide CDs.

Fast Ethernet operates at a data rate of up to 100 Mbps. However, except for the different operating speeds, Fast Ethernet and standard Ethernet are structurally identical. Most applications and protocols that are currently installed on a standard Ethernet system can be seamlessly migrated to a Fast Ethernet system. Because of the equivalence of the two types of Ethernet, mixed Ethernet and Fast Ethernet systems also can be designed and implemented.

The bandwidth required at each workstation connected to a server is generally far less than the bandwidth required at the server. This is because the server might have to handle the bandwidth of multiple workstations at the same time. A cost-effective solution to the bandwidth requirements of this type of system is a mixed Ethernet and Fast Ethernet network. This mixed network consists of standard Ethernet connections at the workstations and Fast Ethernet connections at the servers.

The Ethernet controller is a PCI device, and is therefore a Plug and Play device. You do not have to set any jumpers or configure the controller for the operating system before you use the Ethernet controller.

Notes

1. The Ethernet controller supports the operating

systems that the server supports. To find out which operating systems the server supports, go to the following World Wide Web address:

http://www.ibm.com/pc/us/compat/

If you need additional Ethernet connections, you can install an Ethernet adapter, such as an IBM 10/100 Ethernet adapter. Review the network-adapter documentation for any additional configuration requirements.

Note

If you are installing an IBM 10/100 Ethernet adapter, be sure to run the Ethernet controller diagnostics and record the Ethernet controller configuration information before you install the adapter.

Netfinity 5000 - Type 8659 33

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: The following error messages are

for the Novell NetWare or IntraNetWare server ODI driver. The explanation and recommended action are included with each message.

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

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

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

Explanation: The adapter did not respond when the driver tried to initialize it. Action: Verify that the PCI Ethernet device type is set to the default

(enabled) setting in the Configuration/Setup utility programs (see “PCI bus control” on page 30). If the Ethernet adapter is enabled, go to “Diagnostic test programs” on page 10 to run the diagnostic utility.

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

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 programs. See “PCI bus control” on page 30 for information on setting the interrupt requests. If the IRQ settings are correct, replace the system board.

PCNTNW-NW-066 The cable might be disconnected from the adapter. Explanation: The cable might be disconnected from the server Ethernet port. Action: Verify that a cable is connected to the Ethernet port.

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: If you installed an Ethernet adapter, such as an IBM Netfinity 10/100

Fault Tolerant Adapter, as part of Ethernet redundancy (failover), make sure that the adapter is seated correctly. If the adapter is seated correctly, replace the adapter.

PCNTNW-NW-072 A resource tag is unavailable. Explanation: The driver tried to allocate some resources that were not

available.

Action: Add or free some memory 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.

keyword.

command.

34 Netfinity Server HMM

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: Verify that the PCI Ethernet device type is set to the default

(enabled) position in the Configuration/Setup utility programs (see “PCI bus control” on page 30).

Make sure that the interrupt request numbers are set correctly. If you are using an ISA adapter, make sure resources are reserved as ISA Legacy in the Configuration/Setup utility programs (see “Plug and Play” on page 31.)

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

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.

PCNTNW-NW-079 The Multiple Link Interface Driver (MLID) did not

Explanation: The MSMTx Free Count is not initialized correctly. Action: Restart the server.

PCNTNW-NW-086 The driver parameter block is too small. Explanation: The driver parameter block is too small. Action: Restart the server.

PCNTNW-NW-087 The media parameter block is too small. Explanation: The driver media parameter block is too small. Action: Restart the server.

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 the hardware configuration matches the software settings. See “PCI bus control” on page 30 for information on viewing and changing interrupt requests.

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

Explanation: The IEEE address has a group bit indicating 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 PCI Ethernet device type is set to the default

(enabled) position in the Configuration/Setup utility programs (see “PCI bus control” on page 30). If the Ethernet adapter is enabled, go to “Diagnostic test programs” on page 10 to run the diagnostic utility.

registered with the Link Support Layer (LSL).

initialize MSMTx Free Count.

cleared.

Netfinity 5000 - Type 8659 35

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. Explanation: The driver cannot locate the Ethernet controller on the PCI bus. Action: Verify that the PCI Ethernet device type is set to the default

(enabled) position in the Configuration/Setup utility programs (see “PCI bus control” on page 30).

If the problem persists, go to “Diagnostic test programs” on page 10 to run the diagnostic utility.

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.

NDIS 2.01 (OS/2) driver messages: The

following error messages are for the NDIS 2.01 (OS/2) drivers. The explanation and recommended action are included with each message.

PCNTND-1 Unable to open the Protocol Manager. Explanation: The NDIS stack is not configured correctly. Action: Check and correct the configuration.

PCNTND-6 Out of memory while allocating buffers. Explanation: The driver could not allocate the requested buffers. Action: Check the system configuration. Edit the PROTOCOL.INI file to

reduce the number of Txbuffers and Rxbuffers specified for the driver.

PCNTND-7 A Protocol Manager device error occurred. Explanation: The NDIS stack is not configured correctly. Action: Check and correct the configuration.

PCNTND-8 Bad status for the Protocol Manager. Explanation: The NDIS stack is not configured correctly in the

PROTOCOL.INI file.

Action: Check and correct the 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 the configuration.

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

Explanation: The NDIS stack is not configured correctly in the

PROTOCOL.INI file.

Action: Check and correct the configuration.

PCNTND-11 Protocol Manager registration failed. Explanation: The NDIS stack is not configured correctly. Action: Check and correct the configuration.

failed.

36 Netfinity Server HMM

PCNTND-15 Device not found. Explanation: The driver cannot find an Ethernet controller in the server. Action: Verify that the PCI Ethernet device type is set to the default

PCNTND-16 PCI scan specified, device not found. Explanation: The driver cannot locate the Ethernet controller on the PCI bus. Action: Verify that the PCI Ethernet device type is set to the default

PCNTND-21 The adapter failed the checksum test. Explanation: The driver cannot find an Ethernet controller. Action: Verify that the PCI Ethernet device type is set to the default

PCNTND-23 WARNING: PCNET IRQ found = 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 Routing selection of the System Information menu in the Configuration/Setup Utility. (See “PCI routing” on page 23.)

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 Routing selection of the System Information menu in the Configuration/Setup Utility. (See “PCI routing” on page 23.)

PCNTND-25 PCI scan specified, PCI bus not found! Explanation: The driver cannot locate the PCI bus on the server. Action: Go to “Diagnostic test programs” on page 10 to run the diagnostic

utility.

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

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.

device.

Netfinity 5000 - Type 8659 37

NDIS 4.0 (Windows NT) driver messages:

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

PermaNet(tm) Server: No Secondary Adapter Found. Grouping Mode is

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(tm) Server: Problem Occurs on the Primary Adapter. Switching

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.

PermaNet(tm) 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. .

disabled.

over to the Secondary Adapter.

UNIX messages: The following error messages are

for the SCO UNIX LLI driver.

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 PCI Ethernet device type is set to the default (enabled) position

in the Configuration/Setup utility programs (see “PCI bus control” on page 30). If the problem persists, go to “Diagnostic test programs” on page 10 to run the

diagnostic utility.

pnt0-6 Cannot allocate memory for the adapter during an

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

programs, or run the NETCONFIG program to match the hardware settings.

pnt0-7 Cannot allocate memory for the adapter during reset.

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: Verify that the PCI Ethernet device type is set to the default

interrupt. Please check the Streams parameters.

Please check the Streams parameters.

38 Netfinity Server HMM

pnt0-12 Device failed checksum test! Explanation: The driver cannot find an Ethernet controller. Action: Verify that the PCI Ethernet device type is set to the default

pnt0-13 add_intr_handler failed! Interrupts already enabled. Explanation: The interrupt request (IRQ) that was specified, or the IRQ that

was found, conflicts with other devices in the server. Action: Modify the hardware settings. Run the NETCONFIG program to match the hardware settings.

pnt0-14 Cannot locate hardware. Explanation: The SunSoft Solaris driver cannot find any Ethernet controller. Action: Verify that the PCI Ethernet device type is set to the default

pnt0-15 No more devices to open. Explanation: The SunSoft Solaris driver cannot find any more Ethernet

controllers. Action: Verify that additional Ethernet adapters are present or replace the

Ethernet adapter that fails to respond. If the problem persists, go to “Diagnostic test programs” on page 10 to run the diagnostic utility.

pnt0-17 Device fault...Reset initiated! Explanation: The SunSoft Solaris driver has been reset due to a device

fault. Action: Verify that additional Ethernet adapters are present or replace the

Ethernet adapter that fails to respond. If the problem persists, go to “Diagnostic test programs” on page 10 to run the diagnostic utility.

pnt0-19 IRQ found for PCnet hardware does not match space.c

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