Notification Of A Damaged Recovery Image Or Firmware - ZyXEL Communications UAG Series Cli Reference Manual

34.8 Notification of a Damaged Recovery Image or
Firmware
The UAG's recovery image and/or firmware could be damaged, for example by the power going off
during a firmware upgrade. This section describes how the UAG notifies you of a damaged recovery
image or firmware file. Use this section if your device has stopped responding for an extended
period of time and you cannot access or ping it. Note that the UAG does not respond while starting
up. It takes less than five minutes to start up with the default configuration, but the start up time
increases with the complexity of your configuration.
Use a console cable and connect to the UAG via a terminal emulation program (such as
1
HyperTerminal). Your console session displays the UAG's startup messages. If you cannot see any
messages, check the terminal emulation program's settings (see
restart the UAG.
The system startup messages display followed by "Press any key to enter debug mode within 1
2
seconds."
Note: Do not press any keys at this point. Wait to see what displays next.
Figure 27 System Startup Stopped
BootModule Version: V1.22 | Mar
DRAM: Size = 512 Mbytes
Kernel Version: V2.6.25.4 | 2012-07-13 10:01:15
ZLD Version: V2.50(AACG.0) | 2012-07-20 13:34:43
Press any key to enter debug mode within 1 seconds.
...................................
If the console session displays "Invalid Firmware", or "Invalid Recovery Image", or the console
3
freezes at "Press any key to enter debug mode within 1 seconds" for more than one minute, go to
Section 34.9 on page 226
Figure 28 Recovery Image Damaged
Press any key to enter debug mode within 1 seconds.
.........................................................
Invalid Recovery Image
ERROR
Enter Debug Mode
>
UAG CLI Reference Guide
8 2012 17:12:28
to restore the recovery image.
Chapter 34 File Manager
Section 1.2.1 on page 22) and
225