Using DRD Activate and Deactivate to Recover from Boot Problems

In the event that the administrator needs to boot the drd clone, the system boot can be interrupted
when the message “Press Any Key to interrupt Autoboot” is issued, producing the screen
in
Figure 8.
Figure 8 Boot Menu Obtained by Interrupting the Boot on an Integrity System
/---------------------------------\
/------------------------------\ | System Overview |
| Boot Menu | | hp server rx3600 |
| HP-UX Primary Boot: 0/4/1/0..| | Serial #: USE47059YD |
| HP-UX HA Alternate Boot: 0/4.| | |
| HP-UX Alternate Boot: 0/4/1/.| | System Firmware: 2.03 [4648] |
| Core LAN Gb A | | BMC Version: 5.13 |
| EFI Shell [Built-in] | | MP Version: F.01.58 |
| -----------------------------| | Installed Memory: 4096 MB |
| Boot Configuration | | |
| System Configuration | | CPU Logical |
| Security Configuration | | Module CPUs Speed Status |
| | | 0 2 1.4 GHz Active |
\------------------------------/ | 1 2 1.4 GHz Active |
\----------------------------------/
Choosing “Boot Configuration” displays the screen shown in Figure 9:
Figure 9 Boot Configuration Menu for an Integrity System
/----------------------------------------------------------------------------------\
| Boot Configuration |
| Boot From File |
| Add Boot Entry |
| Edit Boot Entry |
| Remove Boot Entry |
| Edit OS Boot Order |
| AutoBoot Configuration |
| BootNext Configuration |
-------------------------- |
| Driver Configuration |
| Console Configuration |
--------------------------------------------------------------------------------------|
| V |
\------------------------------------------------------------------------------------/
Choosing “Boot From File” initiates a hardware discovery process that displays the screen in
Figure 10, containing the Extensible Firmware Interface addresses.