Chapter 6. Solving Problems

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

You can check the hardware by using the diagnostic test programs a information in this chapter.

Note: When you run the diagnostic test programs, a single problem can several error messages to occur. When this happens, work to cor cause of the first error message. After the cause is correc error messages probably will not occur the next time you run t

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

This chapter contains:

Diagnostic Tools Overview. . . . . . . . . . . . . . . . . . . . . . 109. . . . . . .

Diagnostic LEDs . . . . . . . . . . . . . . . . 109. . . . .

Diagnostic Test Programs. . . . . . . . . . . . . . . . . . . . . .109. . . . . .

Power-OnSelf-Test (POST) . . . . . . . . . . . . . . . . . . . . .110. . . . . .

POST Beep Codes . . . . . . . . . . . . . . . . . . . . . . . . .110. . . . . .

Error Messages . . . . . . . . . . . . . . . . 110. . . . .

Troubleshooting Charts . . . . . . . . . . . . . . 111. . . . .

Option Diskettes . . . . . . . . . . . . . . . . 111. . . . .

Diagnostic Test Programs. . . . . . . . . . . . . . . . . . . . . . . 111. . . . . . .

Navigating Through the Diagnostic .Tests. . . . . . . . . . . . . . 112. . . .

Running Diagnostic Test Programs. . . . . . . . . . . . . . . . . . 112. . . . .

Viewing the Test .Log. . . . . . . . . . . . . . . . . . . . . . .113. . . . . .

Power-on Self Test (POST) Messages. . . . . . . . . . . . . . . . . 114. . . . .

POST Message Table . . . . . . . . . . . . . . . . . . . . . . . 114. . . . . . .

Power-onSelf-Test (POST) Beep Codes. . . . . . . . . . . . . . . . .122. . . .

POST Beep Code Descriptions. . . . . . . . . . . . . . . . . . . .122. . . . .

POST Beep Code Table. . . . . . . . . . . . . . . . . . . . . . 124. . . . . . .

Diagnostic Messages . . . . . . . . . . . . . . . 125. . . . .

Diagnostic Message Tables. . . . . . . . . . . . . . . . . . . . .125. . . . . .

Failed Diagnostic Messages. . . . . . . . . . . . . . . . . . . . .126. . . . . .

Failed Diagnostic Messages That Prevent Proper. .Testing. . . . . . 131.

SCSI Messages . . . . . . . . . . . . . . . . .135. . . .

SCSI Message Table. . . . . . . . . . . . . . . . . . . . . . . .135. . . . . .

Ethernet Controller Messages. . . . . . . . . . . . . . . . . . . . .136. . . . . .

Novell NetWare or IntraNetWare Server ODI Driver. . .Messages. . . .136

NDIS 2.01 (OS/2) Driver Messages. . . . . . . . . . . . . . . . . . 138. . . . .

NDIS 4.0 (Windows NT) Driver Messages. . . . . . . . . . . . . . . 140. . . .

UNIX Messages . . . . . . . . . . . . . . . . 140. . . . .

Troubleshooting . . . . . . . . . . . . . . . . . 143. . . . .

Troubleshooting Charts . . . . . . . . . . . . . . 143. . . . .

Troubleshooting the

10/100 Mbps Ethernet Controller. . . . . . . . . . 149. .

Resolving

Configuration

Conflicts. . . . . . . . . . . . . . . . . . . .152

Resolving Memory-Address

Conflicts. . . . . . . . . . . . . . . . . 152

Changing the Software Configuration . Setup. . . . . . . . . . . . . .152. . .

Changing

the Hardware

Configuration .Setup. . . . . . . . . . . . .152. . .

 Copyright IBM Corp. 1998

 

 

107

Page 115
Image 115
IBM 5000 manual Solving Problems, 107