Compaq ProLiant 8000 ProLiant 8000 Servers Maintenance and Service Guide - Page 213

Redundant ROM Image Recovery, Reset configuration switches 1

Page 213 highlights

6-86 Compaq ProLiant 8000 Servers Maintenance and Service Guide 10. After successful completion of this process, a. Turn off the server. b. Reset configuration switches 1, 4, 5 and 6. (Refer to Configuration Switches Table within this section.) c. Turn on the server as usual. IMPORTANT: If you are performing this procedure on a server with redundant ROM, where both ROM images have been corrupted, repeat the process in succession (once for each corrupt image). If only one image is corrupt, read the following section, "Redundant ROM Image Recovery," for complete instructions. After a failed ROMPaq, power down the server and repeat the above process. Redundant ROM Image Recovery If power is interrupted during the flash process on a server that has redundant ROM, the server should come up as usual (on the same image that it booted) but the inactive (redundant) ROM image will be corrupt. A POST error message displays: 105 - Current System ROM is corrupt - now booting redundant System ROM In this instance, you are required to flash again so that the invalid image is now valid. After you flash the invalid image, the system will boot to that image-which was the original objective.

  • 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

6-86
Compaq ProLiant 8000 Servers Maintenance and Service Guide
10.
After successful completion of this process,
a.
Turn off the server.
b.
Reset configuration switches 1, 4, 5 and 6. (Refer to Configuration Switches Table
within this section.)
c.
Turn on the server as usual.
IMPORTANT:
If you are performing this procedure on a server with redundant ROM, where both ROM
images have been corrupted, repeat the process in succession (once for each corrupt image). If only one
image is corrupt, read the following section,
Redundant ROM Image Recovery,
for complete
instructions.
After a failed ROMPaq, power down the server and repeat the above process.
Redundant ROM Image Recovery
If power is interrupted during the flash process on a server that has redundant ROM, the server
should come up as usual (on the same image that it booted) but the inactive (redundant) ROM
image will be corrupt.
A POST error message displays:
105
Current System ROM is corrupt
now booting redundant System ROM
In this instance, you are required to flash again so that the invalid image is now valid. After you
flash the invalid image, the system will boot to that image-which was the original objective.