Diagnostic Test Programs
POST Error Messages and Beep Codes
POST error messages and beep codes occur during startup when POST finds a
problem with the hardware or detects a change in the hardware configuration. For
more information, see pages 122 through 124.
Diagnostic Error Messages
Diagnostic error 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. For more information, see pages 125 through 134.
Software-Generated Error Messages
These 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 your software.
Troubleshooting Charts
The charts under “Troubleshooting Charts” on page 143 list symptoms of problems
(for example, a symptom might be “The mouse is not working.”), along with steps to
correct the problems.
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 your 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 server. 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.
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.
Chapter 6. Solving Problems
111
