IBM 8685 Hardware Maintenance Manual - Page 42

Viewing the test log, Viewing the System Error log, Diagnostic error message tables

Get IBM 8685 - eServer xSeries 255 PDF manuals and user guides
UPC - 087944957171
View all IBM 8685 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

c. If you run the diagnostic programs with either no mouse or a USB mouse attached to your 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. 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. If the diagnostic programs do not detect any hardware errors but the problem persists 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. 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. 2. To save the test log to a diskette, you must use a diskette that you have formatted yourself; this function does not work with preformatted diskettes. If the diskette has sufficient space for the test log, the diskette may contain other data. Viewing the System Error log You can also view the System Error log from the diagnostic programs. See the instructions in "Viewing error logs from diagnostic programs" on page 30. Diagnostic error message tables For descriptions of the error messages that might appear when you run the diagnostic programs, see "Diagnostic error codes" on page 135. Notes: 1. Depending on your server configuration, some of these error messages might not appear when you run the diagnostic programs. 2. If diagnostic error messages appear that are not listed in the following tables, make sure that your server has the latest levels of BIOS, Advanced System Management Processor, ServeRAID™, and diagnostics microcode installed. Identifying problems using status LEDs Your server has LEDs to help you identify problems with some server components. These LEDs are part of the Light Path Diagnostics built into the server. By following the path of lights, you can quickly identify the type of system error that occurred. 32 xSeries 255 Type 8685: Hardware Maintenance Manual and Troubleshooting Guide

  • 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
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
c.
If you run the diagnostic programs with either no mouse or a USB mouse
attached to your 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. 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.
If the diagnostic programs do not detect any hardware errors but the problem
persists 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.
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.
2.
To save the test log to a diskette, you must use a diskette that you have
formatted yourself; this function does not work with preformatted diskettes. If the
diskette has sufficient space for the test log, the diskette may contain other
data.
Viewing the System Error log
You can also view the System Error log from the diagnostic programs. See the
instructions in “Viewing error logs from diagnostic programs” on page 30.
Diagnostic error message tables
For descriptions of the error messages that might appear when you run the
diagnostic programs, see “Diagnostic error codes” on page 135.
Notes:
1.
Depending on your server configuration, some of these error messages might
not appear when you run the diagnostic programs.
2.
If diagnostic error messages appear that are not listed in the following tables,
make sure that your server has the latest levels of BIOS, Advanced System
Management Processor, ServeRAID
™
, and diagnostics microcode installed.
Identifying problems using status LEDs
Your server has LEDs to help you identify problems with some server components.
These LEDs are part of the Light Path Diagnostics built into the server. By following
the path of lights, you can quickly identify the type of system error that occurred.
32
xSeries 255 Type 8685: Hardware Maintenance Manual and Troubleshooting Guide