Emergency Runtime Image Recovery
Should the RMC runtime image become corrupted or is otherwise deemed unusable, an
emergency recovery mechanism has been placed in the booter. If the situation arises where
this mechanism needs to be utilized, remove power (unplug) from the system and install the
RMC emergency runtime image recovery jumper (J22 pins 11-12) (see Figure 6–5 which
follows). Because this mode requires that the RMC be able to control com1_mode, move
jumper J30 to pins 2-3.
After re-applying power to the system (plug in), the RMC comes up in emergency update
mode, which utilizes only the booter image. Power the system on using the OCP button (the
RMC prompt is not available).
Once at the SRM prompt, use the standard LFU mechanisms to update the runtime image.
At the completion of the update, remove power (unplug) and then remove the RMC
emergency runtime image recovery jumper. If jumper J30 was moved, return it to its initial
position.
NOTE:
1. The booter image cannot be updated while in the emergency runtime image
recovery mode.
2. The amber LEDs on the OCP sequentially blink when updating the RMC
images.
3. When the booter detects that the runtime image is corrupt, the system and fan
fault LEDs will flash on and off in unison. The user must configure the system for
emergency runtime image recovery to correct this problem.
4. When the user configures the system to enter emergency runtime image
recovery mode by adding jumper J22 pins 11-12, all three amber lights flash on
and off in unison until the FW update is started.
5. For a complete listing of OCP LED indications, see Table 7-2.
6-32
hp AlphaServer TS15 Owner’s Guide
