HP NetServer AA 4000 HP Netserver AA Solution Administrator's Guide v - Page 254

B-1, IOP Boot Process in a Windows Endurance Server, IOP tests MIC BIOS

Page 254 highlights

IOPx IOPx is powered on and starts the boot process. IOP passes POST. IOP tests MIC BIOS and calls MIC BIOS. MIC BIOS calls system BIOS. System BIOS starts to load Windows*. Endurance software is loaded. IOP verifies tuple ID. IOPy IOPy is powered on and starts the boot process. IOP passes POST. IOP tests MIC BIOS and calls MIC BIOS. MIC BIOS calls system BIOS. System BIOS starts to load Windows*. Endurance software is loaded. IOP verifies tuple ID. IOP transitions from Offline to Ready. IOPx and IOPy communication is established. IOPs join. IOP transitions from Offline to Ready. CE boot starts. * For an IOP to service the CE boot request, it must have reached the appropriate completed boot. The IOP that services the boot request is one of the following: - If both IOPs are present and are identical, the IOP in the same tuple as the booting CE. - If both IOPs are present and not identical, the IOP with the most current disk services the CE boot request. - If one IOP is available, and if the Endurance server is configured to boot with only that IOP, the only available IOP services the boot request. Figure B-1 IOP Boot Process in a Windows Endurance Server B-2 HP Netserver AA Solution Administrator's Guide

  • 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

B-2
HP Netserver AA Solution Administrator°s Guide
Figure B-1
IOP Boot Process in a Windows Endurance Server
IOP
x
is powered on
and starts the boot
process.
IOP passes POST.
IOP tests MIC BIOS
and calls MIC BIOS.
MIC BIOS calls system
BIOS.
System BIOS starts to
load Windows*.
Endurance software is
loaded.
IOP verifies tuple ID.
IOP transitions from
Offline
to
Ready.
IOP
x
and IOP
y
communication is
established.
IOP
x
IOP
y
is powered on
and starts the boot
process.
IOP passes POST.
IOP tests MIC BIOS
and calls MIC BIOS.
MIC BIOS calls system
BIOS.
System BIOS starts to
load Windows*.
Endurance software is
loaded.
IOP transitions from
Offline
to
Ready.
IOP
y
*
For an IOP to service the CE boot request, it must have reached the appropriate completed
boot. The IOP that services the boot request is one of the following:
- If both IOPs are present and are identical, the IOP in the same tuple as the booting CE.
- If both IOPs are present and not identical, the IOP with the most current disk services the CE
boot request.
- If one IOP is available, and if the Endurance server is configured to boot with only that IOP, the
only available IOP services the boot request.
CE boot starts.
IOPs join.
IOP verifies tuple ID.