IBM Eserver xSeries 360 Type 8686, User Reference Manual

Page: 126 / 184

112
IBM® xSeries 360: User’s Reference
Notes:
a. If the server stops during testing and you cannot continue, restart the server
and try running the diagnostic programs again. If the problem remains, call
for service.
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 no mouse attached to the server, you
will not be able to navigate between test categories using the
Next Cat and
Prev Cat buttons. All other functions that are 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
interface 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.
f. 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 from
the help information and return to where you left off, press Esc.
If the diagnostic programs do not detect any hardware errors but the problem remains
during typical 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.
Error code format
This section shows the format of 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 .)
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 value that is used to verify the validity of the
information.
text message is the diagnostic message that indicates the reason for the
problem.