IBM 865951Y Hardware Maintenance Manual - Page 13

General Checkout, A system might be part of a cluster if

Page 13 highlights

General Checkout The server diagnostic programs are stored in nonvolatile random-access memory (NVRAM) 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 port, and parallel port. 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 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. Netfinity 5000 - Type 8659 5

  • 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

General Checkout
The server diagnostic programs are stored in nonvolatile
random-access memory (NVRAM) 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 port, and
parallel port.
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
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.
Netfinity 5000 - Type 8659
5