Cisco Cisco Packet Data Interworking Function (PDIF)
System Recovery
▀ Prerequisites
▄ ASR 5000 System Administration Guide, StarOS Release 16
232
Prerequisites
Successful recovery from a failed reboot requires that you have access to the system via a console port, and have an
uncorrupted copy of the StarOS boot image file stored in flash memory on the management card, or accessible from an
external memory device.
uncorrupted copy of the StarOS boot image file stored in flash memory on the management card, or accessible from an
external memory device.
Console Access
The boot recovery sequence can only be executed via a terminal connected to the serial console port on the active
management card. This connection can be through a terminal server that is accessible via a LAN interface.
management card. This connection can be through a terminal server that is accessible via a LAN interface.
The boot recovery sequence can only be viewed via the Console port.
Boot Image
The boot recovery command line interface allows you to specify from which boot image you would like to boot the
system. If the system failed to reload following a software update, you can initiate a boot from a previously stored
image.
system. If the system failed to reload following a software update, you can initiate a boot from a previously stored
image.
The system recovery procedure will prompt you to enter the path name for the location of the StarOS boot image from
which the system will boot. By default the boot command will timeout and attempt to reload the highest priority image
from flash memory using the default configuration file.
which the system will boot. By default the boot command will timeout and attempt to reload the highest priority image
from flash memory using the default configuration file.
The operating system software is delivered as a single binary file (.bin file extension) and is loaded as a single instance
for the entire system.
for the entire system.
For StarOS releases prior to 16.1, the image filename is identified by its release version and corresponding build
number. Format = production.<build_number>.<platform>.bin.
For StarOS release 16.1 onwards, the image filename is identified by its platform type and release number.
Format = <platform>-<release_number>.bin.
Refer to the Configuring the Boot Stack section in the Software Management Operations chapter for additional
information on boot stack entries and prioritization.
information on boot stack entries and prioritization.