Redundant rom support, Safety and security benefits, Access to redundant rom settings – HP DL385 User Manual
Page 84
Server software and configuration utilities 84
IMPORTANT: You must install and use HP SIM to benefit from the Pre-Failure Warranty for processors,
SAS and SCSI hard drives, and memory modules.
For additional information, refer to the Management CD in the HP ProLiant Essentials Foundation Pack or
the HP SIM websit
Redundant ROM support
The server enables you to upgrade or configure the ROM safely with redundant ROM support. The server
has a 4-MB ROM that acts as two, separate 2-MB ROMs. In the standard implementation, one side of the
ROM contains the current ROM program version, while the other side of the ROM contains a backup
version.
NOTE: The server ships with the same version programmed on each side of the ROM.
Safety and security benefits
When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a
backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted
for any reason. This feature protects the existing ROM version, even if you experience a power failure
while flashing the ROM.
Access to redundant ROM settings
To access the redundant ROM through RBSU:
1.
Access RBSU by pressing the F9 key during powerup when the prompt is displayed in the upper
right corner of the screen.
2.
Select Advanced Options.
3.
Select Redundant ROM Selection.
4.
Select the ROM version.
5.
Press the Enter key.
6.
Press the Esc key to exit the current menu or press the F10 key to exit RBSU. The server restarts
automatically.
To access the redundant ROM manually:
1.
Power down the server (on page
2.
Remove the access panel ("
3.
Set positions 1, 5, and 6 of the system maintenance switch to On.
4.
5.
Power up the server (on page
6.
Wait for the server to emit two beeps.
7.
Repeat steps 1 and 2.
8.
Set positions 1, 5, and 6 of the system maintenance switch to Off.
9.
Repeat steps 4 and 5.
When the server boots, the system identifies whether the current ROM bank is corrupt. If a corrupt ROM is
detected, the system boots from the backup ROM and alerts you through POST or IML that the ROM bank
is corrupt.
If both the current and backup versions of the ROM are corrupt, the server automatically enters ROMPaq
disaster recovery mode.