IBM 6000R Hardware Maintenance Manual - Page 13

General checkout

Get IBM 6000R - Netfinity - 8682 PDF manuals and user guides
UPC - 087944534341
View all IBM 6000R manuals
Add to My Manuals
Save this manual to your list of manuals

Page 13 highlights

General checkout The server diagnostic programs are stored in upgradable read-only memory (ROM) on the system board. These programs are the primary method of testing the major components of the server: The system board, Ethernet controller, video controller, RAM, keyboard, mouse (pointing device), diskette drive, serial ports, hard drives, and parallel port. You can also use them to test some external devices. See "Diagnostic programs and error messages" on page 16. Also, if you cannot determine whether a problem is caused by the hardware or by the software, you can run the diagnostic programs to confirm that the hardware is working properly. When you run the diagnostic programs, a single problem might cause several error messages. When this occurs, work to correct the cause of the first error message. After the cause of the first error message is corrected, the other error messages might not occur the next time you run the test. A failed system might be part of a shared DASD cluster (two or more systems sharing the same external storage device(s)). Prior to running diagnostics, verify that the failing system is not part of a shared DASD cluster. A system might be part of a cluster if: • The customer identifies the system as part of a cluster. • One or more external storage units are attached to the system and at least one of the attached storage units is additionally attached to another system or unidentifiable source. • One or more systems are located near the failing system. If the failing system is suspected to be part of a shared DASD cluster, all diagnostic tests can be run except diagnostic tests which test the storage unit (DASD residing in the storage unit) or the storage adapter attached to the storage unit. Notes: 1. For systems that are part of a shared DASD cluster, run one test at a time in looped mode. Do not run all tests in looped mode, as this could enable the DASD diagnostic tests. 2. If multiple error codes are displayed, diagnose the first error code displayed. 3. If the computer hangs with a POST error, go to the "Symptom-to-FRU index" on page 153. 4. If the computer hangs and no error is displayed, go to "Undetermined problems" on page 186. 5. Power supply problems, see "Symptom-to-FRU index" on page 153. 6. Safety information, see "Safety information" on page 196. 1

  • 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
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
1
General checkout
The server diagnostic programs are stored in upgradable
read-only memory (ROM) on the system board.
These pro-
grams are the primary method of testing the major compo-
nents of the server:
The system board, Ethernet controller,
video controller, RAM, keyboard, mouse (pointing device),
diskette drive, serial ports, hard drives, and parallel port.
You can also use them to test some external devices.
See
“Diagnostic programs and error messages” on page 16.
Also, if you cannot determine whether a problem is caused
by the hardware or by the software, you can run the diag-
nostic programs to confirm that the hardware is working
properly.
When you run the diagnostic programs, a single problem
might cause several error messages.
When this occurs,
work to correct the cause of the first error message.
After
the cause of the first error message is corrected, the other
error messages might not occur the next time you run the
test.
A failed system might be part of a shared DASD cluster (two
or more systems sharing the same external storage
device(s)).
Prior to running diagnostics, verify that the failing
system is not part of a shared DASD cluster.
A system might be part of a cluster if:
•
The customer identifies the system as part of a cluster.
•
One or more external storage units are attached to the
system and at least one of the attached storage units is
additionally attached to another system or unidentifi-
able source.
•
One or more systems are located near the failing sys-
tem.
If the failing system is suspected to be part of a shared
DASD cluster, all diagnostic tests can be run except diag-
nostic tests which test the storage unit (DASD residing in the
storage unit) or the storage adapter attached to the storage
unit.
Notes:
1.
For systems that are part of a shared DASD cluster, run
one test at a time in looped mode.
Do not run all tests
in looped mode, as this could enable the DASD diag-
nostic tests.
2.
If multiple error codes are displayed, diagnose the first
error code displayed.
3.
If the computer hangs with a POST error, go to the
“Symptom-to-FRU index” on page 153.
4.
If the computer hangs and no error is displayed,
go to
“Undetermined problems” on page 186.
5.
Power supply problems, see “Symptom-to-FRU index”
on page 153.
6.
Safety information, see “Safety information” on page
196.