> System Recovery
> 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 reload command.
> This chapter includes the following sections:

> • | Prerequisites

> • | Accessing the boot CLI

> • | Booting from a Selected Image

> Caution: 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.
> 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 SMC, or accessible from an external PCMCIA memory device.
> Console Access
> The boot recovery sequence can only be executed via a terminal connected to the serial console port on the active SPIO 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.
> 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.
> A boot image binary file name uses the following format:
> production.build_number.asr5000.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 CLI
> To access the boot CLI you must interrupt an in-progress reload (reboot) sequence.
> Caution: 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.
> Initiate a Reboot
> A reload can be initiated in one of two ways:

> • | Power cycle the chassis – Turn the circuit breakers on the power filter units (PFUs) Off (0) and then On (I).

> • | Execute a reload command

> [local]asr5000# reload -noconfirm
> The boot sequence displays messages on the terminal as it steps through its processes.
> Interrupt the Boot Sequence
> When the “Booting priority” message line appears (and not before), press CTRL+C to break out of the boot process as shown in the example below:
> Booting priority 8
> image : /flash/production.35272.st40.bin
> config: /flash/system.cfg
> Entry at 0x000000000cba45e0
> Press CTRL+C at this point in the sequence.
> A message similar to the following appears after the boot process has been interrupted:
> *******9/0 Ctrl-C Pressed-------------------------------------------------------
> Failed.
> aborted by user
> 8/0:boot>
> Enter CLI Mode
> With the boot prompt displayed, enter cli to access the boot recovery CLI. The CLI prompt changes as shown below:
> 8/0:boot>cli
> 8/0:cli>
> boot Command Syntax
> The boot recovery command has the following syntax:
> boot [ -show | -priority=* | -config=* | -noconfig ] { bootfile_URL }
> The options for this command include:

> • | -show: displays the current boot configuration

> • | -priority=*: selects the desired boot stack priority (*)

> • | -config=*: enters the desired configuration filename (*), if not the default file

> • | -noconfig: boots using no configuration file

> bootfile_URL is the URL for the location of the StarOS boot image file. It specifies the path and file name of the StarOS .bin file from which the system will be booted.
> The URL may refer to a local file (flash) or an external file on a PCMCIA device attached to the SMC. The URL must be entered in the following format:
> { /flash | /pcmcia1 /filename
> Booting from a Selected Image
> You will issue a boot command via the boot CLI to initiate the system recovery process.
> Boot Using No Configuration FIle
> 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/production.41731.asr5000.bin
> The boot sequence ends with a prompt to enter the Quick Setup Wizard for creating a configuration file.
> Launching StarOS
> Starting program at 0x0000000000100000
> Starent Networks ASR5000 Intelligent Mobile Gateway
> SMC is starting up..............................
> Starting software <version> <build_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 configure command followed by the URL for the configuration file as shown in the example below:
> [local]asr5000# 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:
> 8/0:cli>boot -config=/flash/system.cfg /flash/production.41731.asr5000.bin
> The boot sequence ends with the appearance of the CLI prompt.
> [local]asr5000#
> Confirm that the desired configuration has loaded by running the Exec mode show configuration command.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883