IBM 88614RX Maintenance Manual - Page 33

Starting the diagnostic programs, Viewing the test log, Extended, Basic, Notes, Next Cat, Prev Cat

Page 33 highlights

Starting the diagnostic programs This section describes the general procedure to run 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 from help, press Esc. Complete the following steps to start the diagnostic programs: 1. Turn on the server and watch the screen. 2. When the message Press F1 for Configuration/Setup, Press F2 for Diagnostics appears, press F2. If a power-on password is set, the server prompts you for it. Type the power-on password, and press Enter. 3. When the Diagnostic Programs screen appears, select either Extended or Basic from the top of the screen. 4. Select the test you want to run from the list that appears; then, follow the instructions on the screen. 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, replace the component that was being tested when the server stopped. 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 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. 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. If the diagnostic programs do not detect any hardware error but the problem remains during normal server operations, a software error might be the cause. If you suspect a software problem, see the information that comes with the software package. Diagnostic error codes are listed in "Diagnostic error codes" on page 95. Viewing the test log When the tests are completed, you can view the test log by selecting Utility from the top of the screen and then selecting View Test Log. Notes: 1. You can view the test log only while you are in the diagnostic programs. When you exit the diagnostic programs, the test log is cleared (saved test logs are not affected). To save the test log so that you can view it later, click Save Log on the diagnostic programs screen and specify a location and name for the saved log file. Chapter 3. Diagnostics 23

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212

Starting the diagnostic programs
This section describes the general procedure to run 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 from help, press Esc.
Complete the following steps to start the diagnostic programs:
1.
Turn on the server and watch the screen.
2.
When the message
Press F1 for Configuration/Setup, Press F2 for
Diagnostics
appears, press F2.
If a power-on password is set, the server prompts you for it. Type the power-on
password, and press Enter.
3.
When the Diagnostic Programs screen appears, select either
Extended
or
Basic
from the top of the screen.
4.
Select the test you want to run from the list that appears; then, follow the
instructions on the screen.
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,
replace the component that was being tested when the server stopped.
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 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. 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.
If the diagnostic programs do not detect any hardware error but the problem
remains during normal server operations, a software error might be the cause. If
you suspect a software problem, see the information that comes with the software
package.
Diagnostic error codes are listed in “Diagnostic error codes” on page 95.
Viewing the test log
When the tests are completed, you can view the test log by selecting
Utility
from
the top of the screen and then selecting
View Test Log
.
Notes:
1.
You can view the test log only while you are in the diagnostic programs. When
you exit the diagnostic programs, the test log is cleared (saved test logs are not
affected). To save the test log so that you can view it later, click
Save Log
on
the diagnostic programs screen and specify a location and name for the saved
log file.
Chapter 3. Diagnostics
23