IBM 86595RY Hardware Maintenance Manual - Page 16

Diagnostic tools, Diagnostic test programs

Page 16 highlights

Diagnostic tools Server problems can be caused by the hardware, the software, or a user error. An example of a user error is pressing the wrong key on the keyboard. You can check the hardware by using the diagnostic test programs and the information in this section. 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. If the hardware is OK and you have not made an error, you might have a software problem. If you suspect that you have a software problem, refer to the information that comes with that software package. Diagnostic tools overview The following tools are available to help identify and resolve hardware-related problems: LEDs on the system board and power supplies Diagnostic test programs Power-on self-test (POST) POST beep codes Error messages Troubleshooting charts Option diskettes Diagnostic LEDs: When a system error occurs, the relevant LEDs on the system board are lighted to identify where the errors are (see "System board LEDs" on page 142). When you see the System Error LED illuminated on the operator LED (status) panel on the front of the server, check the LEDs on the power supplies and at any Ethernet adapters, then open the cover and see which LEDs are illuminated on the system board. Diagnostic test programs: The server diagnostics test programs are stored in nonvolatile random-access memory (NVRAM) on the system board. These programs are the primary method of testing the system board, memory, and other standard features of the Netfinity 5000. You can also use them to test some external devices. Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the test programs to confirm that the hardware is working properly. 8 Netfinity Server HMM

  • 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

Diagnostic tools
Server problems can be caused by the hardware, the
software, or a user error.
An example of a user error is
pressing the wrong key on the keyboard.
You can check the hardware by using the diagnostic test
programs and the information in this section.
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.
If the hardware is OK and you have not made an error,
you might have a software problem.
If you suspect that
you have a software problem, refer to the information that
comes with that software package.
Diagnostic tools overview
The following tools are available to help identify and
resolve hardware-related problems:
±
LEDs on the system board and power supplies
±
Diagnostic test programs
±
Power-on self-test (POST)
±
POST beep codes
±
Error messages
±
Troubleshooting charts
±
Option diskettes
Diagnostic LEDs:
When a system error occurs, the
relevant LEDs on the system board are lighted to identify
where the errors are (see “System board LEDs” on
page
142).
When you see the System Error LED
illuminated on the operator LED (status) panel on the front
of the server, check the LEDs on the power supplies and
at any Ethernet adapters, then open the cover and see
which LEDs are illuminated on the system board.
Diagnostic test programs:
The server
diagnostics test programs are stored in nonvolatile
random-access memory (NVRAM) on the system board.
These programs are the primary method of testing the
system board, memory, and other standard features of the
Netfinity 5000. You can also use them to test some
external devices.
Also, if you cannot determine whether a problem is caused
by the hardware or by the software, you can run the test
programs to confirm that the hardware is working properly.
8
Netfinity Server HMM