IBM 86655RY Hardware Maintenance Manual - Page 34

Diagnostic programs and error messages, ipssend format, format, Notes

Page 34 highlights

3. Use ipssend format to restart the format of the physical drive. The syntax is: ipssend format controller channel sid where: • controller is the ServeRAID controller number (1-12) • channel is the channel number for the device (1, 2, or 3) • sid is the SCSI ID for the device (0-15) After the format is complete, the ServeRAID controller will be able to recognize the drive again. Recovering from a failure in a failover-environment In a failover environment, when the ServeRAID device driver is unable to send a command to the primary controller and the primary controller does not respond to a reset command, the device driver attempts to failover to the secondary controller. Note: Loose cables or defective physical drives will not cause a failover to occur. Replacing a non-hot-plug controller in a failover pair If a failed controller is not in a hot-plug PCI slot, do the following to replace it: 1. Shutdown the server. 2. Replace the failed controller. 3. Reconfigure the new controller. Notes: 1.Be sure the firmware level of the new controller is the same as the controller you are replacing. Be sure to use the same controller name, partner name, and SCSI initiator ID for the controller you are replacing. 2.For detailed instructions, refer to the Hardware Maintenance Manual for the ServeRAID controller being serviced. If the failed controller is in a hot-plug slot, refer to the documentation that comes with the server for instructions for replacing the controller. Diagnostic programs and error messages 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. Diagnostic error messages indicate that a problem exists; they are not intended to be used to identify a failing part. Troubleshooting and servicing of complex problems that are indicated by error messages should be performed by trained service personnel. Sometimes the first error to occur causes additional errors. In this case, the server displays more than one error message. Always follow the suggested action instructions for the first error message that appears. The following sections contain the error codes that might appear in the detailed test log and summary log when running the diagnostic programs. The error code format is as follows: 24 Hardware Maintenance Manual: Netfinity 7600 - Type 8665 Models 1RY, 2RY

  • 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
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294

24
Hardware Maintenance Manual: Netfinity 7600
Type 8665 Models 1RY, 2RY
3.
Use
ipssend format
to restart the format of the physical drive.
The syntax is:
ipssend format
controller channel sid
where:
controller
is the ServeRAID controller number (1
12)
channel
is the channel number for the device (1, 2, or 3)
sid
is the SCSI ID for the device (0
15)
After the
format
is complete, the ServeRAID controller will be able to recognize
the drive again.
Recovering from a failure in a failover-environment
In a failover environment, when the ServeRAID device driver is unable to send a
command to the primary controller and the primary controller does not respond to a
reset command, the device driver attempts to failover to the secondary controller.
Note:
Loose cables or defective physical drives will not cause a failover to occur.
Replacing a non-hot-plug controller in a failover pair
If a failed controller is not in a hot-plug PCI slot, do the following to replace it:
1.
Shutdown the server.
2.
Replace the failed controller.
3.
Reconfigure the new controller.
Notes:
1.Be sure the firmware level of the new controller is the same as the controller you are
replacing.
Be sure to use the same controller name, partner name, and SCSI
initiator ID for the controller you are replacing.
2.For detailed instructions, refer to the Hardware Maintenance Manual for the
ServeRAID controller being serviced.
If the failed controller is in a hot-plug slot, refer to the documentation that comes with
the server for instructions for replacing the controller.
Diagnostic programs and error messages
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.
Diagnostic error messages indicate that a problem exists; they are not intended to be
used to identify a failing part.
Troubleshooting and servicing of complex problems
that are indicated by error messages should be performed by trained service
personnel.
Sometimes the first error to occur causes additional errors.
In this case, the server
displays more than one error message.
Always follow the suggested action
instructions for the
first
error message that appears.
The following sections contain the error codes that might appear in the detailed test
log and summary log when running the diagnostic programs.
The error code format is as follows: