This chapter describes how to recover a system after it has failed to
complete a reboot following a power off cycle or interruption of the normal
boot sequence following a
This system recovery process interrupts subscriber service by
dropping any existing flows and preventing traffic from being processed during
the boot interval. It should only be initiated as an emergency measure.
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.
Boot recovery 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. Boot recovery can only be viewed via the console port.
The boot recovery command line interface enables 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.
The system recovery process 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.
The StarOS software is delivered as a single binary file (.bin file extension) and is loaded as a single instance 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.
Accessing the boot
To access the boot
CLI you must interrupt an in-progress reload (reboot) sequence.
This system recovery
process interrupts subscriber service by dropping any existing flows and
preventing traffic from being processed during the boot interval. It
should only be initiated as an emergency measure.
This procedure boots
the system using the specified boot image without also loading a configuration
file. A sample command string appears below:
8/0:cli>boot -noconfig /flash/image_filename.bin
The boot sequence
ends with a prompt to enter the Quick Setup Wizard for creating a configuration
Launching StarOSStarting program at 0x0000000000100000Starent Networks ASR5500 Intelligent Mobile Gatewaymanagement_card is starting up..............................Starting software image_version_number...No configuration found, press enter to continue. 1. Do you wish to continue with the Quick Setup Wizard[yes/no]:
You can exit the
Quick Setup Wizard by entering
no in response
to the above prompt. Load a desired configuration file using the Exec mode
command followed by the URL for the configuration file as shown in the example
[local]host_name# configure /flash/system.cfg
Boot Using A
Specified Configuration File
This procedure boots
the system using the specified boot image and configuration file. A sample
command string appears below: