HP Surestore Disk Array 12h System Administrator's Guide for HP-UX, MPE, and W - Page 165

Using the ARDIAG Offline Diagnostic on MPE, Operating environment

Page 165 highlights

MPE Chapter 7. Using the ARDIAG Offline Diagnostic on MPE This chapter defines the AutoRAID supported offline diagnostic commands for Series 800 MPE systems. This functionality will be a combination of the support media offline diagnostic environment (ODE) commands and commands issued from the AutoRAID front panel. Operating environment ARDIAG will only operate under ODE and thus it only operates in an offline environment. When ARDIAG is executed, ODE handles all the I/O with the user and it handles several higher level commands like LOG, HELP, etc. NOTE. There should be no I/O activity on the SCSI bus when using ARDIAG. When operating in a multi-initiator environment, make sure none of the host systems are trying to access the disk array. Bus activity make cause ARDIAG to not see the disk array. Support Software ARDIAG requires all the software needed for ODE to run as ARDIAG relies on ODE to load and run. Additionally, ARDIAG needs the MAPPER SL and the DIODE SL from the protocol level down. Minimum hardware For ARDIAG to run properly, a working I/O subsystem and at least one SureStore E Disk Array is needed. ARDIAG must also meet ODE's hardware requirements (for example a working console). ARDIAG and ODE will use no more than 4 MB of main memory. Minimum software ODE, MAPPER SL and DIODE SL are needed to execute ARDIAG correctly. 165

  • 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

165
MPE
Chapter 7.
Using the ARDIAG Offline
Diagnostic on MPE
This chapter defines the AutoRAID supported offline diagnostic commands for Series 800 MPE systems.
This functionality will be a combination of the support media offline diagnostic environment (
ODE
)
commands and commands issued from the AutoRAID front panel.
Operating environment
ARDIAG will only operate under ODE and thus it only operates in an offline environment. When ARDIAG
is executed, ODE handles all the I/O with the user and it handles several higher level commands like LOG,
HELP, etc.
NOTE.
There should be no I/O activity on the SCSI bus when using ARDIAG. When
operating in a multi-initiator environment, make sure none of the host systems are
trying to access the disk array. Bus activity make cause ARDIAG to not see the
disk array.
Support Software
ARDIAG requires all the software needed for ODE to run as ARDIAG relies on ODE to load and run.
Additionally, ARDIAG needs the MAPPER SL and the DIODE SL from the protocol level down.
Minimum hardware
For ARDIAG to run properly, a working I/O subsystem and at least one SureStore E Disk Array is needed.
ARDIAG must also meet ODE’s hardware requirements (for example a working console). ARDIAG and
ODE will use no more than 4 MB of main memory.
Minimum software
ODE, MAPPER SL and DIODE SL are needed to execute ARDIAG correctly.