Cisco IOS XR ROM Monitor Guide, Release 3.4
Router Recovery with ROM Monitor
Downloads: This chapterpdf (PDF - 489.0KB) The complete bookPDF (PDF - 1.33MB) | Feedback

Router Recovery with ROM Monitor

Table Of Contents

Router Recovery with ROM Monitor

About ROMMON Installation Files

Locating Installable Files

tar Filenames and Version Numbers

vm Filenames and Version Numbers

About Turboboot

About the Boot Device (Destination Disk)

Reinstalling Cisco IOS XR Software on Cisco CRS-1 Routers

Cisco CRS-1 Router Installation Overview

Installation from a TFTP Server

Installation from a Local Storage Device

Reinstalling to a Cisco CRS-1 Router from a TFTP Server Image

Restrictions for TFTP Services

Prerequisites

Examples

Reinstalling to a Cisco CRS-1 Router from an Image on a Local Storage Device

Prerequisites

Examples

What to Do Next

Reinstalling Cisco IOS XR Software on Cisco XR 12000 Series Routers

Cisco XR 12000 Series Router Installation Overview

Installation from a TFTP Server

Installation from a Local Storage Device

About Boothelper in Cisco XR 12000 Series Routers

Boothelper Procedures (Cisco XR 12000 Series Routers)

Starting the Router with Boothelper

Examples

Configuring the Management Ethernet Interface

Prerequisites

Exiting Boothelper and Starting ROM Monitor

Reinstalling to a Cisco XR 12000 Series Router from a TFTP Server Image

Restrictions for TFTP Services

Prerequisites

Examples

Reinstalling to a Cisco XR 12000 Series Router from an Image on a Local Storage Device

Prerequisites

Examples

What to Do Next

Bringing Up Non-DSC PRPs on Cisco XR 12000 Series Routers

Prerequisites


Router Recovery with ROM Monitor


The standard way to install new software on the DSC is by using the install command in administration EXEC mode. However, if the DSC is unable to boot the Cisco IOS XR software or you want to completely replace the existing software, you can reinstall the software while the DSC is in ROM Monitor mode. When you install the Cisco IOS XR software from ROM Monitor mode, you must use a special software installation file with a vm file extension. These files are called vm files. You cannot install software in package installation envelope (PIE) files from ROM Monitor mode.


Note Installation using a vm file in ROM Monitor mode should be performed only from the DSC of the system.



Caution Reinstalling the Cisco IOS XR software from ROMMON replaces the currently installed router software and causes substantial router downtime. We recommend installing or upgrading software packages from EXEC mode using PIE files, as described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

This chapter contains the following sections:

About ROMMON Installation Files

About Turboboot

About the Boot Device (Destination Disk)

Reinstalling Cisco IOS XR Software on Cisco CRS-1 Routers

Reinstalling Cisco IOS XR Software on Cisco XR 12000 Series Routers

Bringing Up Non-DSC PRPs on Cisco XR 12000 Series Routers

About ROMMON Installation Files

This section includes the following topics:

Locating Installable Files

tar Filenames and Version Numbers

vm Filenames and Version Numbers

Locating Installable Files

To obtain Cisco IOS XR software and version information, use the Cisco IOS XR Software Selector tool at the following website:

http://www.cisco.com/cgi-bin/Software/IOXPlanner/planner-tool/ioxplanner.cgi?

The Cisco IOS XR Software Selector tool allows you to browse for your software upgrade from a single interface. You can display and select software by package name, release, or platform. The tool also includes posting images and Extensible Markup Language (XML) schemas. Choosing a platform, release, or software feature automatically limits the choices based on your selection until you arrive at your preferred software.

The software packages that you can install from ROMMON are listed in Table 2-1.

Table 2-1 Downloadable Software for Installation from ROM Monitor

Software Package Name
Description

Cisco IOS XR IP/MPLS Core Software

This package contains two copies of the Cisco IOS XR Unicast Routing Core Bundle. One copy is in the package installation envelope (PIE) file format and can be installed while Cisco IOS XR is running, as described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide. The other copy is in a vm file that can be installed from ROM Monitor. This package also includes the Cisco IOS XR MPLS, Manageability, and Multicast packages (in PIE files).

Cisco IOS XR IP/MPLS Core Software 3DES

This package contains everything in the Cisco IOS XR IP/MPLS Core Software package, and it contains the Cisco IOS XR Security package (in a PIE file).


The packages listed in Table 2-1 are distributed in files with tar filename extensions (tar files are assembled with the UNIX tar utility). When you download a tar file, you must unpack the tar file with a software program before you can install any of the files in the package.

The files that you can install from ROM Monitor have a vm filename extension. These files contain the software included in the Cisco IOS XR Unicast Routing Core Bundle. The other files in the packages are PIE files.


Note The tar files contain both PIE files and vm files. If the router is operating properly, you can install the software using the appropriate PIE file with little or no interruption to router traffic, as described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide. If the router cannot boot the Cisco IOS XR software, install the core software using the vm file first, then install any additional packages using the PIE files after the router enters EXEC mode.


Packages for the Cisco XR 12000 Series Router contain additional files which are described in Table 2-2.

Table 2-2 Additional Files for the Cisco XR 12000 Series Router 

Filename
Description

mbiprp-rp.vm-3.4.0

This software is for all performance route processors (PRPs) except the DSC and must be loaded on a PRP before it can communicate with the DSC.

bfprp_romupgrade-1.14.0.91

This software is for the ROM Monitor upgrade of the PRP cards, and later versions may display a different version number at the end of the filename. For instructions on installing this software, see "Upgrading and Downgrading Boothelper and ROM Monitor on Cisco XR 12000 Series Routers".

c12kprp-boot-mz.120-32.S3

This software is the Boothelper for the PRP cards, and later versions may display a different version number at the end of the filename. For instructions on installing this software, see "Upgrading and Downgrading Boothelper and ROM Monitor on Cisco XR 12000 Series Routers".


tar Filenames and Version Numbers

The format for a tar filename is:

platform-bundle_name-major.minor.maintenance.tar

The tar filename components are described in Table 2-3.

Table 2-3 tar Filename Components 

Component
Description

platform

Identifies the platform for which the software package is designed.

For packages designed for the Cisco CRS-1 router, the platform designation is "CRS-1."

For packages designed for the Cisco XR 12000 Series Router, the platform designation is "XR12000."

bundle_name

Identifies a specific bundle.

The "iosxr" bundle name indicates a file that includes all packages in the Cisco IOS XR Unicast Routing Core Bundle and the Management, MPLS, and Multicast packages.

These packages are described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

The "iosxr-k9" bundle name indicates a file that includes all packages in the "iosxr" bundle file plus the Security package.

major

Identifies the major release of this package.

A major release occurs when there is a major architectural change to the product (for example, a major new capability is introduced).

All packages operating on the router must be at the same major release level.

A major release is the least frequent release and may require a router reboot.

minor

Identifies the minor release of this package.

A minor release contains one or more of the following:

New features

Bug fixes

The minor release version does not have to be identical for all software packages operating on the router, but the operating packages must be certified by Cisco as compatible with each other.

A minor release may require a router reboot.

maintenance

Identifies the maintenance release of this package.

A maintenance release contains a collection of bug fixes for a package.

The maintenance release version does not have to be identical for all software packages operating on the router, but the major and minor versions of the maintenance release must match the those of the package being updated.

A maintenance release usually does not require a router reboot.


vm Filenames and Version Numbers

The format for a composite vm filename for Cisco CRS-1s is:

comp-platform-package_name.vm-major.minor.maintenance

The format for a vm filename for Cisco XR 12000 Series Routers is:

platform-package_name.vm-major.minor.maintenance

The "comp" prefix indicates that the file is a composite of multiple packages. The other filename components are described in Table 2-4.

Table 2-4 vm Filename Components 

Component
Description

platform

Identifies the platform for which the software package is designed.

For packages designed for Cisco CRS-1s, the platform designation is "hfr."

For packages designed for Cisco XR 12000 Series Routers, the platform designation is "c12k."

The mbiprp platform name specifies a special file for the Cisco XR 12000 Series Router. This file is described in Table 2-2.

package_name

Identifies a specific package.

The "mini" package name indicates a composite package that includes all packages in the Cisco IOS XR Unicast Routing Core Bundle, which is described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

The rp package name specifies a special file for the Cisco XR 12000 Series Router. This file is described in Table 2-2.

major

Identifies the major release of this package.

A major release occurs when there is a major architectural change to the product (for example, a major new capability is introduced).

All packages operating on the router must be at the same major release level.

A major release is the least frequent release and may require a router reboot.

minor

Identifies the minor release of this package.

A minor release contains one or more of the following:

New features

Bug fixes

The minor release version does not have to be identical for all software packages operating on the router, but the operating packages must be certified by Cisco as compatible with each other.

A minor release may require a router reboot.

maintenance

Identifies the maintenance release of this package.

A maintenance release contains a collection of bug fixes for a package.

The maintenance release version does not have to be identical for all software packages operating on the router, but the major and minor versions of the maintenance release must match the those of the package being updated.

A maintenance release usually does not require a router reboot.


About Turboboot

The Turboboot environmental variable automates the software installation process in ROM Monitor mode and determines the installation settings, such as the boot device (destination disk) for software installation. The following is the syntax for the Turboboot environmental variable:

TURBOBOOT=on, {boot-device},[format | clean]

In the following example, the Turboboot variable is set to on, the boot device (destination disk) is the flash disk in disk0:, and the installation process will format the disk.

TURBOBOOT=on,disk0,format
 
   

There are three main arguments and keywords for the Turboboot variable:

on: Installs and activates the Cisco IOS XR software packages when the RP is booted with the vm image

boot-device: selects the destination disk for software installation. See the "About the Boot Device (Destination Disk)" section for more information.

[format | clean]: When the clean option is selected, the Cisco IOS XR software is completely replaced, but all other files on the disk are preserved, including configuration files for each secure domain router (SDR). When the format option is selected, the Cisco IOS XR software is completely replaced, and only the admin configuration is preserved. All other files on the disk, including all configuration files for the SDRs, and all user files, are deleted. The admin configuration contains the configuration that determines SDR names and inventory. The SDR configurations include router configurations such as BGP and interface configurations.


Note Each argument is separated by a comma (,).


For more information, see Environment Variable Settings.

About the Boot Device (Destination Disk)

When you install the Cisco IOS XR software using the Turboboot method in ROM Monitor mode, you must specify a boot-device for the router. The boot device is the local disk on the RP where the software is installed.

On the Cisco CRS-1, the supported boot devices are disk0 and disk1. If a boot-device is not specified, disk0 is used by default. If disk0 is not installed, then disk1 will be used.

On the Cisco XR 12000 Series Router, the supported boot devices are disk0, disk1, and compact flash.

See the "About Turboboot" section for more information on Turboboot usage and syntax.

The boot-device determines the slot where all software will be installed on all RPs and distributed route processors (DRPs) that act as the designated secure domain router system controllers (DSDRSCs). In other words, when you Turboboot the Cisco IOS XR software to the DSC, all the other RPs in the system must include a disk in that same slot. The system uses these disks to distribute the software to each RP in the system. In addition, any additional software or software upgrades are automatically saved to the same boot device.

Once the Cisco IOS XR software is installed to the boot device using the Turboboot method, all additional software and software upgrades are automatically installed and synced to that same boot device and cannot be changed. For example:

If the RP is Turbobooted with disk0 (TURBOBOOT=on,disk0), then all packages are installed to disk0: and the boot device is "disk0:".

If the RP is Turbobooted with disk1 (TURBOBOOT=on,disk1), then all packages are installed to disk1: and the boot device is "disk1:".

On a Cisco XR 12000 Series Router, you can also Turboboot using compact flash disk as the boot device.

Once you boot the Cisco IOS XR software, you are not allowed to add packages to anywhere other than the boot device. For example, you cannot boot the DSC to disk1: and decide to add your packages to disk0: or vice versa.


Note We recommend using disk0 as the boot device. Disk0 is preinstalled in most RPs, which ensures that the correct disk is used to store the software packages on the entire system.


Reinstalling Cisco IOS XR Software on Cisco CRS-1 Routers


Caution Reinstalling Cisco IOS XR software from ROMMON replaces the currently installed router software and causes substantial router downtime. We recommend installing or upgrading software packages from the EXEC mode using package installation envelope (PIE) files, as described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

This section includes the following topics:

Cisco CRS-1 Router Installation Overview

Reinstalling to a Cisco CRS-1 Router from a TFTP Server Image

Reinstalling to a Cisco CRS-1 Router from an Image on a Local Storage Device

What to Do Next

Cisco CRS-1 Router Installation Overview

When you reinstall the software from ROM Monitor mode, you can do either of the following procedures:

Load the Cisco IOS XR software from a vm file on a TFTP server to the DSC.

Transfer the vm file to a local storage device and then load the Cisco IOS XR software from that storage device to the DSC.

The following sections provide an overview of the processes:

Installation from a TFTP Server

Installation from a Local Storage Device

Installation from a TFTP Server

When you install Cisco IOS XR software from a TFTP server to the DSC, you must perform the following procedures:

1. Back up the router configuration while still in EXEC mode.

2. Verify the sanity of the configuration file system on each SDR using the command cfs check.

3. Place all RPs and DRPs in ROM Monitor mode.

4. From ROM Monitor mode, clear the ROM Monitor environmental variables on all RPs, including the DSC.

5. On the DSC, configure the IP parameters for the Management Ethernet interface. This is performed with the card in ROM Monitor, and is required to access the TFTP server.

6. On the DSC, configure the TURBOBOOT environment variable to either clean or format the boot disk during the installation. The recommended boot device is disk0:.

7. On the DSC, boot the Cisco IOS XR software from a vm file on the TFTP server.

8. Reset all other RPs to boot the Cisco IOS XR software.

After you boot the Cisco IOS XR software, the Turboboot process will either clean or format the boot device, based on the TURBOBOOT environment variable setting.


Caution If the Turboboot variable is set to format the boot device, all SDR configurations are deleted: only the admin configuration is preserved. Review the sections About Turboboot and About the Boot Device (Destination Disk) for more information.

For the procedure to install Cisco IOS XR software from a TFTP server, see the "Reinstalling to a Cisco CRS-1 Router from a TFTP Server Image" section.

Installation from a Local Storage Device

When you install Cisco IOS XR software from a local storage device, you must perform the following procedures:

1. Back up the router configuration while still in EXEC mode.

2. Verify the sanity of the configuration file system on each SDR using the command cfs check.

3. Copy the required vm file to the DSC flash disk that will hold the installable file. We recommend using disk1. You can also replace the flash disk with a flash disk that already has the correct image.

4. Place all RPs and DRPs in ROM Monitor mode.

5. From ROM Monitor mode, clear the ROM Monitor environmental variables on all RPs, including the DSC.

6. On the DSC, configure the TURBOBOOT environment variable to either clean or format the boot disk during the installation. The recommended boot device is disk0:.

7. Turboboot the DSC with the vm image located on the local storage device.

8. Reset all other RPs to boot the Cisco IOS XR software.


Caution If the Turboboot variable is set to format the boot device, all existing SDR configurations are deleted. Only the Admin configuration is preserved. Review the sections About Turboboot and About the Boot Device (Destination Disk) for more information.

For the procedure to install Cisco IOS XR software from a local storage device, see the "Reinstalling to a Cisco CRS-1 Router from an Image on a Local Storage Device" section.

Reinstalling to a Cisco CRS-1 Router from a TFTP Server Image

Cisco IOS XR software can be reinstalled directly from a vm file located on a TFTP server. Complete the instructions in this section exactly as described.

Restrictions for TFTP Services

TFTP services by some vendors (such as Sun Solaris) may not support files larger than 32 MB. Because most Cisco IOS XR vm images are larger than 32 MB, you may need to use one of the following options:

Use a third-party or freeware TFTP server that supports file sizes larger than 32 MB.

Download a patch from Sun Microsystems to correct this limitation (http://www.sun.com).

Install the Cisco IOS XR software from a vm image located on the local flash disk. See the "Reinstalling to a Cisco CRS-1 Router from an Image on a Local Storage Device" section.

Prerequisites

Before reinstalling Cisco IOS XR software from a TFTP server image, verify that the following prerequisites have been met:

Cisco CRS-1 routers running Cisco IOS XR Software Release 3.4.0 or higher require ROM Monitor release 1.42. See ROM Monitor Compatibility with Cisco IOS XR Software for more information.

Before you begin, collect the following information.

IP address of the Management Ethernet interface on the DSC

Subnet mask of the Management Ethernet interface on the DSC

IP address of the default gateway that serves your router

IP address of the TFTP server from which the software will be downloaded

The filename and directory of the vm installation file that will be installed on the router

Determine the boot device for your system. See About the Boot Device (Destination Disk) for more information.


Note This procedure installs the Cisco IOS XR software on a router that previously ran the Cisco IOS XR software. If you are upgrading a Cisco XR 12000 Series Router that is currently running Cisco IOS software, you need to first upgrade the router to Cisco IOS XR software, as described in the document titled Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.


SUMMARY STEPS

1. Back up the router configuration while still in EXEC mode.

2. Verify the sanity of the configuration file system:.

a. cfs check

b. Repeat on each SDR in the system.

3. Place all RPs in ROM Monitor mode:

a. admin

b. config-register 0x0 location all

c. reload location all

4. Clear the ROM Monitor environmental variables on all RPs, including the DSC:

a. unset BOOT

b. unset TFTP_FILE

c. sync

d. Repeat for each RP in the system (line card chassis and fabric chassis).

5. On the DSC, set the environment variables that configure the Management Ethernet interface for use in ROM Monitor mode:

a. IP_ADDRESS=ip_address

b. IP_SUBNET_MASK=mask

c. DEFAULT_GATEWAY=ip_address

6. Set the Turboboot variables on the DSC:

a. TURBOBOOT=on, disk0, options

b. sync

7. On the DSC, boot the vm image located on the tftp server:
boot tftp://server/directory/filename

8. Reset all other RPs to boot the Cisco IOS XR software:

a. confreg 0x2

b. reset

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Back up the router configuration while still in EXEC mode.

(Optional) To preserve the current router configuration, copy it to another disk while still in EXEC mode.

See the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide for more information.

Step 2 

Verify the sanity of the configuration file system. Repeat on each SDR in the system.

cfs check

Example

RP/0/RP0/CPU0:router# cfs check

(Optional) Verifies the sanity of the router configuration, and resolves any internal inconsistencies.

Repeat the cfs check command on each SDR in the system.

Note This step is only necessary if you wish to preserve the router configurations (if Turboboot is set to clean). If Turboboot is set to format, then the disk will be erased and the existing configurations will be deleted. The default option is clean.

Step 3 

Place all RPs in ROM Monitor mode:

admin

config-register 0x0 location all

reload location all

Example

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# config-register 0x0 location all

RP/0/RP0/CPU0:router(admin)# reload location all

See Resetting the Configuration Register and Reloading a DSC to ROM Monitor Mode for more information.

Step 4 

Clear the ROM Monitor environmental variables on all RPs, including the DSC.

unset BOOT

unset TFTP_FILE

sync

Example

rommon B1> unset BOOT

rommon B2> unset TFTP_FILE

rommon B3> sync

Ensures all RPs in the system are prepared for Turboboot. Repeat for each RP in the system (line card chassis and fabric chassis).

Enter the settings exactly as shown. You must attach a terminal to each card for this procedure.

All variable names are case sensitive.

a. Clears the BOOT variable.

b. Clears the TFTP_FILE variable.

c. Saves the changes.

Note If the unset command displays an error message, it is most likely because the variable you are trying to change is not set. If this is the case, ignore the message and continue.

Step 5 

On the DSC, sets the environment variables that configure the Management Ethernet interface for use in ROM Monitor mode:

IP_ADDRESS=ip_address

IP_SUBNET_MASK=mask

DEFAULT_GATEWAY=ip_address

Example

rommon B4> IP_ADDRESS=1.1.1.1
rommon B5> IP_SUBNET_MASK=255.255.254.0
rommon B6> DEFAULT_GATEWAY=1.1.0.1

Enter these settings exactly as shown. All variable names are case sensitive.

a. Sets the IP address for the Management Ethernet interface on the DSC.

b. Sets the subnet mask for the Management Ethernet interface on the DSC.

c. Identifies the default gateway that serves the DSC.

Step 6 

On the DSC, set the Turboboot variables:

TURBOBOOT=on, boot-device, options

sync

Example

rommon B7> TURBOBOOT=on,disk0,format

rommon B8> sync

Sets the TURBOBOOT parameters and saves the configuration. Separate each parameter with a comma (,).

To enable the Turboboot process, specify on.

Specify a boot device where all software will be installed on the DSC and all DSDRSCs. We recommend disk0.

To replace the existing software without formatting the boot device, replace options with clean.

To replace the existing software and format the boot device, replace options with format.

The default option is clean.

Any existing configuration is preserved.

Step 7 

On the DSC, boot the vm image located on the tftp server:

boot tftp://server/directory/filename

Example

rommon B9> boot tftp://223.255.254.254/softdir/comp-hfr-mini.vm

Retrieves the file from the TFTP server and installs it on the boot disk.

Run this command on the DSC and specify the vm installation file from the TFTP server.

This process removes any existing software packages, resets the configuration register to 0x2, and boots the DSC.

Allow the system to fully boot. The TURBOBOOT process takes some time. Do not enter any commands until you are prompted to enter a username or until the CLI prompt appears.

The "Press RETURN to get started" message appears twice. The first occurrence appears when the software is loaded into memory. The second occurrence happens after the software has been installed on the disk.

The DSC is fully booted when the following message appears:

SYSTEM CONFIGURATION COMPLETED

Step 8 

Reset all other RPs to boot the Cisco IOS XR software:

confreg 0x2

reset

Example

rommon B4> confreg 0x2

rommon B5> reset

a. Sets the configuration register to automatically start the boot process instead of staying in ROM Monitor mode.

b. Resets the RP and starts the boot process.

The RPs synchronize the new Cisco IOS XR software from the DSC.

Examples

Verify the sanity of the configuration file system on each SDR in the system:

RP/0/RP0/CPU0:router# cfs check
 
   

Place all RPs in ROM Monitor mode:

RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0 location all 
RP/0/RP0/CPU0:router(admin)# reload location all
 
   

Clear the ROM Monitor environmental variables on all RPs, including the DSC:

rommon B1> unset BOOT
rommon B2> unset TFTP_FILE
rommon B3> sync
 
   

Set the IP Environment Variables to configure the ROM Monitor Management Ethernet interface on the DSC:

rommon B4> IP_ADDRESS=10.1.1.1
rommon B5> IP_SUBNET_MASK=255.255.254.0
rommon B6> DEFAULT_GATEWAY=10.1.0.1
 
   

Turboboot the DSC. The following example shows how to boot the router using the specified vm file on the specified TFTP server:

rommon B7> TURBOBOOT=on,disk0,format
rommon B8> sync
rommon B9> boot tftp://10.10.10.10/software/comp-hfr-mini.vm-3.4.0
 
   

Reset all other RPs to boot the Cisco IOS XR software:

rommon B8> confreg 0x2
rommon B9> reset

Reinstalling to a Cisco CRS-1 Router from an Image on a Local Storage Device

This section describes the tasks required to install Cisco IOS XR software on the boot device using a vm image stored on a local storage device. The local storage device can be either of the removable flash disks in disk0 or disk1. We recommend using disk1 as the storage device for the vm image, and disk0 as the boot device (destination disk).

Complete the procedures exactly as described in this section.


Note Before booting begins on the DSC, a delay of 10 minutes or more may occur while the vm image is read to memory from the removable local storage device.


Prerequisites

A valid vm image, as described in the "Locating Installable Files" section, must be located on a flash disk installed the RP. We recommend using disk1:.

If this file is not present on a local disk or a different version is required, use one of the following options:

Cisco CRS-1 routers running Cisco IOS XR Software Release 3.4.0 or higher require ROM Monitor release 1.40. See ROM Monitor Compatibility with Cisco IOS XR Software for more information.

While the router is still in EXEC mode, copy the necessary vm image from a TFTP, an FTP, or an rcp server to disk0 or disk1. This process is described in the "Upgrading and Managing Cisco IOS XR software" chapter of Cisco IOS XR Getting Started Guide. See specifically the section "Obtaining and Placing Cisco IOS XR Software".

Consult your system administrator for a flash disk containing the bootable vm file.

Consult your Cisco representative for a flash disk containing the bootable vm file. See Obtaining Additional Publications and Information for more information.


Note The removable flash disk used to store the installation file should be used to store archives only of vm and PIE files. This disk cannot be used as a destination for installed software or configurations. Only the boot device can be used to store active software and configurations. See the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide. See specifically the section "Overview of Package Management" for more information.


SUMMARY STEPS

1. Back up the router configuration while still in EXEC mode.

2. Verify the sanity of the configuration file system:

a. cfs check

b. Repeat on each SDR in the system.

3. Copy the required vm file to the DSC flash disk that will hold the installable file. We recommend using disk1. You can also replace the flash disk with a flash disk that already has the correct image.

4. Place all RPs in ROM Monitor mode:

a. admin

b. config-register 0x0 location all

c. reload location all

5. Clear the ROM Monitor environmental variables on all RPs, including the DSC:

a. unset BOOT

b. unset TFTP_FILE

c. sync

d. Repeat for each RP in the system (line card chassis and fabric chassis).

6. Set the Turboboot variables on the DSC:

a. TURBOBOOT=on, disk0, options

b. sync

7. On the DSC, boot the vm image located on the local storage device:
boot device:/filename

8. Reset all other RPs to boot the Cisco IOS XR software:

c. confreg 0x2

d. reset

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Back up the router configuration while still in EXEC mode.

(Optional) To preserve the current router configuration, copy it to another disk while still in EXEC mode.

See the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide for more information.

Step 2 

Verify the sanity of the configuration file system. Repeat on each SDR in the system.

cfs check

Example

RP/0/RP0/CPU0:router# cfs check

(Optional) Verifies the sanity of the router configuration, and resolves any internal inconsistencies.

Repeat the cfs check command on each SDR in the system.

Note This step is only necessary if you wish to preserve the router configurations (if Turboboot is set to clean). If Turboboot is set to format, then the disk will be erased and the existing configurations will be deleted. The default option is clean.

Step 3 

Copy the required vm file to the DSC flash disk, or replace the flash disk with a flash disk that has the correct image.

Places the software on the router in preparation for installation.

We recommend using flash disk1: to hold the installable file.

For more information, see the "Prerequisites" section for this procedure.

Step 4 

Place all RPs in ROM Monitor mode:

admin

config-register 0x0 location all

reload location all

Example

RP/0/RP0/CPU0:router# admin

RP/0/RP0/CPU0:router(admin)# config-register 0x0 location all

RP/0/RP0/CPU0:router(admin)# reload location all

See Resetting the Configuration Register and Reloading a DSC to ROM Monitor Mode for more information.

Step 5 

Clear the ROM Monitor environmental variables on all RPs, including the DSC.

unset BOOT

unset TFTP_FILE

sync

Example

rommon B1> unset BOOT

rommon B2> unset TFTP_FILE

rommon B3> sync

Ensures all RPs in the system are prepared for Turboboot. Repeat for each RP in the system (line card chassis and fabric chassis).

Enter the settings exactly as shown. You must attach a terminal to each card for this procedure.

All variable names are case sensitive.

a. Clears the BOOT variable.

b. Clears the TFTP_FILE variable.

c. Saves the changes.

Note If the unset command displays an error message, it is most likely because the variable you are trying to change is not set. If this is the case, ignore the message and continue.

Step 6 

On the DSC, set the Turboboot variables:

TURBOBOOT=on, boot-device, options

sync

Example

rommon B7> TURBOBOOT=on,disk0,format

rommon B8> sync

Sets the TURBOBOOT parameters and saves the configuration. Separate each parameter with a comma (,).

To enable the Turboboot process, specify on.

Specify a boot device where all software will be installed on the DSC and all DSDRSCs. We recommend disk0.

To replace the existing software without formatting the boot device, replace options with clean.

To replace the existing software and format the boot device, replace options with format.

The default option is clean.

Any existing configuration is preserved.

Step 7 

On the DSC, boot the vm image located the local storage device:

boot devixe:/filename

Example

rommon B7> boot disk1:/comp-hfr-mini.vm-3.4.0

Boots the file located on the local storage device and installs it to the boot disk.

This process removes any existing software packages, resets the configuration register to 0x2, and boots the system.

Allow the RP to fully boot. The "Press RETURN to get started" message appears twice. The first occurrence appears when the software is loaded into memory. The second occurrence happens after the software has been installed on the disk.

The system is fully booted when the following message appears:

SYSTEM CONFIGURATION COMPLETED
 
        

Note A delay of 10 minutes or more occurs while the software is read from the flash disk.

Step 8 

Reset all other RPs to boot the Cisco IOS XR software:

confreg 0x2

reset

Example

rommon B4> confreg 0x2

rommon B5> reset

a. Sets the configuration register to automatically start the boot process instead of staying in ROM Monitor mode.

b. Resets the RP and starts the boot process.

The RPs synchronize the new Cisco IOS XR software from the DSC.

Examples

Verify the sanity of the configuration file system on each SDR in the system:

RP/0/RP0/CPU0:router# cfs check
 
   

Place all RPs in ROM Monitor mode:

RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# config-register 0x0 location all 
RP/0/RP0/CPU0:router(admin)# reload location all
 
   

Clear the ROM Monitor environmental variables on all RPs, including the DSC:

rommon B1> unset BOOT
rommon B2> unset TFTP_FILE
rommon B4> sync
 
   

Turboboot the DSC:

rommon B5> TURBOBOOT=on,disk0,format
rommon B6> sync
rommon B7> boot disk1:/comp-hfr-mini.vm-3.4.0 

Note A delay of 10 minutes or more occurs while the software is read from the flash disk.


Reset all other RPs to boot the Cisco IOS XR software:

rommon B8> confreg 0x2
rommon B9> reset

What to Do Next

After the system is up and in EXEC mode, you can execute the full range of CLI commands from the DSC.


Note If there was no previous router configuration, you must enter a root-system username and password when the boot process is complete.


After reinstalling the software, you might want to verify interfaces, install additional packages or perform other configuration tasks:

1. For instructions to verify that the interfaces are up and properly configured, see "Verifying the System Interfaces" in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

2. Install additional software from the PIE files, as necessary. See "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide for more information.

3. See Cisco Technical Support & Documentation Website for a list of the additional documentation required to fully configure the router.

Reinstalling Cisco IOS XR Software on Cisco XR 12000 Series Routers


Caution Reinstalling the Cisco IOS XR software from ROMMON replaces the currently installed router software and causes substantial router downtime. We recommend installing or upgrading software packages from the EXEC mode using package installation envelope (PIE) files, as described in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

This section includes the following topics:

Cisco XR 12000 Series Router Installation Overview

About Boothelper in Cisco XR 12000 Series Routers

Boothelper Procedures (Cisco XR 12000 Series Routers)

Reinstalling to a Cisco XR 12000 Series Router from a TFTP Server Image

Reinstalling to a Cisco XR 12000 Series Router from an Image on a Local Storage Device

What to Do Next

Cisco XR 12000 Series Router Installation Overview

To reinstall the software from ROM Monitor mode, perform either of the following procedures:

Installation from a TFTP Server: use this method to boot the Cisco IOS XR software from a vm file located on a TFTP server.

Installation from a Local Storage Device: use this method to first transfer the vm file to a local storage device and then boot the Cisco IOS XR software from that local storage device.

Installation from a TFTP Server

To install the Cisco IOS XR software from a TFTP server, perform the following procedures:

1. Start the DSC Boothelper and either configure or verify the configuration of the Management Ethernet interface on the PRP to which you are installing the software.

2. Place the DSC in ROM Monitor mode.

3. Clear any environment variables that might interfere with the installation.

4. Configure the TURBOBOOT environment variable to either clean or format the boot device during the installation.

5. Boot the Cisco IOS XR software from a vm file on the TFTP server. After you boot the Cisco IOS XR software, the Turboboot process will either clean or format the boot device based on the TURBOBOOT environment variable setting.

6. Boot the standby DSC and all other PRPs with the MBI.


Caution If the Turboboot variable is set to format the boot device, all SDR configurations are deleted. Only the admin configuration is preserved. Review the sections About Turboboot and About the Boot Device (Destination Disk) for more information.

For the procedure to install the Cisco IOS XR software from a TFTP server, see the "Reinstalling to a Cisco XR 12000 Series Router from a TFTP Server Image" section.

Installation from a Local Storage Device

To install the Cisco IOS XR software from a local storage device, perform the following procedures:

1. Copy the new Cisco IOS XR software to the local storage device on the DSC. We recommend disk1.

2. Place the router in ROM Monitor mode.

3. Clear any environment variables that might interfere with the installation.

4. Configure the TURBOBOOT environment variable to either clean or format the boot device during the installation.

5. Boot the new Cisco IOS XR software from the image on the local storage device. After you boot the Cisco IOS XR software, the Turboboot process will either clean or format the boot device based on the TURBOBOOT environment variable setting.

6. Boot the standby DSC and all other PRPs with the MBI.


Caution If the Turboboot variable is set to format the boot device, all SDR configurations are deleted. Only the admin configuration is preserved. Review the sections About Turboboot and About the Boot Device (Destination Disk) for more information.

For the procedure to install the Cisco IOS XR software from a local storage device (such as disk1), see the "Reinstalling to a Cisco XR 12000 Series Router from an Image on a Local Storage Device" section.

About Boothelper in Cisco XR 12000 Series Routers

Boothelper software is additional software that extends the capabilities of ROM Monitor on a Cisco XR 12000 Series Router. With Boothelper, ROM Monitor can load images from compact flash and TFTP servers. Without Boothelper, ROM Monitor can only load images from a local storage device (disk0, disk1, and bootflash).

Before you can use Boothelper to connect to remote devices, such as a TFTP server, you must configure the Management Ethernet interface in the Boothelper software. After Boothelper is configured, you do not need to load the software. When the configuration register is set to load software (setting 0x2102), the software is loaded in the following sequence:

1. ROM Monitor

2. Boothelper

3. Cisco IOS XR software

If the Boothelper software cannot load, the ROM Monitor prompt appears. If the Cisco IOS XR software cannot load, the Boothelper prompt appears as follows:

router(boot)>
 
   

If all the software loads correctly, the Cisco IOS XR software prompt appears.

Boothelper Procedures (Cisco XR 12000 Series Routers)

This section provides the following procedures for use on Cisco XR 12000 Series routers:

Starting the Router with Boothelper

Configuring the Management Ethernet Interface

Exiting Boothelper and Starting ROM Monitor

Starting the Router with Boothelper

In normal operating conditions, it should not be necessary to start the router with Boothelper. If you want to reinstall software from a vm image on a remote server, you must start Boothelper to verify or configure the Management Ethernet interface. See About Boothelper in Cisco XR 12000 Series Routers for more information.

SUMMARY STEPS

1. Restart the router in ROM Monitor mode.

2. confreg 0x0

3. reset

4. unset BOOT

5. unset BOOTLDR=
or
set BOOTLDR=bootflash:/filename

6. sync

7. boot

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Restart the router in ROM Monitor mode.

Restarts the router in ROM Monitor mode.

For more information, see Entering ROM Monitor Mode.

Step 2 

confreg 0x0

Example

rommon 1 > confreg 0x0

Configures the router to restart in ROM Monitor mode.

This step and the next are not necessary if you have already set the configuration register to 0x0 in Step 1.

Step 3 

reset

Example

rommon 2 > reset

Activates the configuration change made in Step 2.

Step 4 

unset BOOT

Example

rommon 3 > unset boot

Clears the setting of the BOOT environment variable.

If the router has been running Cisco IOS XR software, the BOOT variable is probably set to load that software.

Step 5 

unset BOOTLDR=

or

set BOOTLDR=bootflash:/filename

Example

rommon 2 > unset BOOTLDR=

or

rommon 2 > set BOOTLDR=bootflash:/c12kprp-boot-mz

Configures ROM Monitor to load the Boothelper software.

unset BOOTLDR=
If the Boothelper file is the first file in bootflash (dir bootflash:), it will automatically be loaded when the boot command is run. Unset the Boothelper if the Boothelper file is the first file in bootflash.

set BOOTLDR=bootflash:/filename
If the Boothelper file is not the first file in bootflash, set the bootflash variable to specify the name and location of the Boothelper file.

Step 6 

sync

Example

rommon 3 > sync

Saves the configuration change in Step 4.

Step 7 

boot

Example

rommon 3 > boot

Boots the Boothelper software.

Examples

Starting the Router with Boothelper: Example

The following example shows how to start the router with Boothelper:

rommon 1 > confreg 0x0
 
   
 
   
rommon 2 > reset
 
   
System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 512M found, Slot 2: 1024M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
rommon 1 > unset BOOT
 
   
rommon 2 > unset BOOTLDR=
rommon 3 > sync
 
   
rommon 4 > boot
 
   
Self decompressing the image : BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB [OK]
 
   
              Restricted Rights Legend
 
   
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
 
   
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
 
   
 
   
 
   
Cisco Internetwork Operating System Software 
IOS (tm) GS Software (C12KPRP-BOOT-M), Version 12.0(31)S, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Sat 16-Apr-05 22:45 by kellythw
Image text-base: 0x00010000, data-base: 0x0095D000
 
   
cisco 12410/PRP (MPC7450) processor (revision 0x00) with 1572864K bytes of memo.
MPC7450 CPU at 665Mhz, Rev 2.1, 256KB L2, 2048KB L3 Cache
Last reset from sw reset
 
   
3 Route Processor Cards
2 Clock Scheduler Cards
5 Switch Fabric Cards
1 8-port OC3 POS controller (8 POS).
1 four-port OC12 POS controller (4 POS).
1 OC48 POS controller (1 POS).
2 Four Port Gigabit Ethernet/IEEE 802.3z controllers (8 GigabitEthernet).
2 Ethernet/IEEE 802.3 interface(s)
8 GigabitEthernet/IEEE 802.3 interface(s)
13 Packet over SONET network interface(s)
2043K bytes of non-volatile configuration memory.
 
   
1000944K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
65536K bytes of Flash internal SIMM (Sector size 256K).
.
.
.
Press RETURN to get started!
 
   
 
   
router(boot)>

Configuring the Management Ethernet Interface

To enable network communications when the Cisco IOS XR software is not loaded, you must configure the Management Ethernet interface in Boothelper. The Boothelper configuration is most often used to enable access to TFTP servers when reinstalling software from vm files.

Prerequisites

Before you begin, collect the following information:

IP address of the Management Ethernet interface for your RP

Subnet mask of the Management Ethernet interface for your RP

IP address of the default gateway that serves your RP

SUMMARY STEPS

1. Start the Boothelper software.

2. enable

3. Enter the password.

4. show interface ethernet interfaceNumber

5. configure terminal

6. interface ethernet interfaceNumber

7. ip address ipaddress subnetmask

8. mac-address macaddress

9. no ip directed-broadcast

10. no ip route-cache

11. no shutdown

12. end

13. ip default-gateway ipAddress

14. reload

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Start the Boothelper software.

Starts the Boothelper.

For more information, see the "Starting the Router with Boothelper" section.

Step 2 

enable

Example:

router(boot)> enable

Places the router in privileged EXEC mode.

Step 3 

Enter the password.

Example:

Password:

Submits the password for authentication.

The password is not displayed on the screen.

Step 4 

show interface ethernet interfaceNumber

Example:

router(boot)# show interface ethernet 0

Displays the current interface configuration and statistics for the specified interface.

Enter 0 for Ethernet interface 0 or 1 for Ethernet interface 1.

Enter 3 for Ethernet interface 3 on a PRP-2 card only.

If the current configuration is correct, skip to Step 13.

Step 5 

configure terminal

Example:

router(boot)# configure terminal

Places the router in configuration mode.

Step 6 

interface ethernet interfaceNumber

Example:

router(b(config)# interface ethernet 0

Selects an interface to configure.

Enter 0 for Ethernet interface 0 or 1 for Ethernet interface 1.

Note The Ethernet ports correspond to the Management Ethernet interfaces in the Cisco IOS XR software. For example, Ethernet 0 corresponds to MgmtEth0/x/CPU0/0 in the Cisco IOS XR software.

Step 7 

ip address ipaddress subnetmask

Example:

router(b(config-if)# ip address 10.8.28.103 
255.255.0.0

Configures the IP address and subnet mask for the interface.

Replace ipaddress with the IP address for the interface.

Replace subnetmask with the subnet mask for the interface.

Step 8 

mac-address macaddress

Example:

router(b(config-if)# mac-address 0007.b39b.a7ff

Configures the MAC address for the interface.

Replace macaddress with the MAC address for the interface.

This MAC address applies only while the node is running Boothelper.

Step 9 

no ip directed-broadcast

Example:

router(b(config-if)# no ip directed-broadcast

Disables the translation of a directed broadcast to physical broadcasts.

Step 10 

no ip route-cache

Example:

router(b(config-if)# no ip route-cache

Disables all switching options supported by the ip route-cache command.

Step 11 

no shutdown

Example:

router(b(config-if)# no shutdown

Brings up the interface.

Step 12 

end

Example:

router(b(config-if)# end

Exits interface configuration mode.

Step 13 

ip default-gateway ipAddress

Example:

router(b(config)# ip default-gateway 10.10.0.1

Defines the IP address for the default gateway.

Step 14 

reload

Example:

router(boot)# reload
 
        
System configuration has been modified. Save? 
[yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]

Restarts the RP.

Type Y and press Return to save the configuration.

Press Return when asked to confirm that you want to reload the router.

Because the configuration register is still set to 0x0, the router reloads ROM Monitor.

Examples

Example: Configuring the Management Ethernet Interface

The following example shows how to configure Management Ethernet interface 0 on a PRP in Boothelper:

router(boot)> enable
 
   
Password: 
 
   
router(boot)# show interface ethernet 0
 
   
Ethernet0 is administratively down, line protocol is down 
  Hardware is 10/100 Ethernet, address is 0007.b39b.a7ff (bia 0007.b39b.a7ff)
  Internet address is 12.8.28.103/16
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Queueing strategy: fifo
  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     1 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
 
   
router(boot)# configure terminal
 
   
Enter configuration commands, one per line.  End with CNTL/Z.
 
   
router(b(config)# interface ethernet 0
 
   
router(b(config-if)# ip address 10.8.28.103 255.255.0.0
 
   
router(b(config-if)# mac-address 0007.b39b.a7ff
 
   
router(b(config-if)# no ip directed-broadcast
 
   
router(b(config-if)# no ip route-cache
 
   
router(b(config-if)# no shutdown
 
   
router(b(config-if)# end
 
   
router(boot)# reload
 
   
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]
 
   
System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 512M found, Slot 2: 1024M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
rommon 1 > 

Exiting Boothelper and Starting ROM Monitor

If an RP is running Boothelper software and you want to return to ROM Monitor mode, use the following procedure.

SUMMARY STEPS

1. enable

2. Enter the password.

3. configure terminal

4. config-register 0x0

5. exit

6. reload

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

router(boot)> enable

Places the router in privileged EXEC mode.

Step 2 

Enter the password.

Example:

Password:

Submits the password for authentication.

The password is not displayed on the screen.

Step 3 

configure terminal

Example:

router(boot)# configure terminal

Places the RP in configuration mode.

Step 4 

config-register 0x0

Example:

router(b(config)# config-register 0x0

Configures the RP to start in ROM Monitor mode when the next reload occurs.

Step 5 

exit

Example:
router(b(config)# exit

Exits configuration mode.

Step 6 

reload

Example:

router(boot)# reload
 
        
System configuration has been modified. Save? 
[yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]

Restarts the RP.

Type Y and press Return to save the configuration.

Press Return when asked to confirm that you want to reload the router.

Because the configuration register is set to 0x0, the router reloads ROM Monitor.

Examples

The following example is provided:

Exiting Boothelper and Starting ROM Monitor

Exiting Boothelper and Starting ROM Monitor

The following example shows how to exit Boothelper and start ROM Monitor on an RP:

router(boot)> enable
 
   
Password: 
 
   
router(boot)# configure terminal
 
   
Enter configuration commands, one per line.  End with CNTL/Z.
 
   
router(b(config)# config-register 0x0
 
   
router(b(config)# exit
 
   
router(boot)# reload
 
   
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK][OK][OK]
Proceed with reload? [confirm]
 
   
System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEVELOPMENT 
SOFTWARE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 512M found, Slot 2: 1024M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
rommon 1 >

Reinstalling to a Cisco XR 12000 Series Router from a TFTP Server Image

The Cisco IOS XR software can be reinstalled directly from a vm file located on a TFTP server. Complete the instructions in this section exactly as described.

Restrictions for TFTP Services

TFTP services by some vendors (such as Sun Solaris) may not support files larger than 32 MB. Because most Cisco IOS XR vm images are larger than 32 MB, you may need to use one of the following options:

Use a third-party or freeware TFTP server that supports file sizes larger than 32 MB.

Download a patch from Sun Microsystems to correct this limitation (http://www.sun.com).

Install the Cisco IOS XR software from a vm image located on the local flash disk. See the "Reinstalling to a Cisco XR 12000 Series Router from an Image on a Local Storage Device" section.

Prerequisites

The following hardware and software are required:

ROM Monitor 1.14 or higher

Boothelper c12kprp-boot-mz.120-32.S3

256 MB or higher flash disk0

Before you begin, collect the following information.

IP address of the TFTP server from which the software will be downloaded

The filename and directory of the vm installation file that will be installed on the router


Note This procedure installs the Cisco IOS XR software on a router that previously ran the Cisco IOS XR software. If you are upgrading a Cisco XR 12000 Series Router that is currently running Cisco IOS software, you need to first upgrade the router to Cisco IOS XR software, as described in Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.


SUMMARY STEPS

1. Back up the router configuration while still in EXEC mode.

2. Place both the DSC and standby DSC in ROM Monitor mode.

3. Configure Boothelper for network access.

4. set

5. unset BOOT

6. unset TFTP_FILE

7. unset CONFIG_FILE

8. TURBOBOOT=on, boot-device, options

9. sync

10. boot tftp://server/directory/filename

11. Boot all non-DSC PRPs with the MBI.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Back up the router configuration while still in EXEC mode.

(Optional) To preserve the current router configuration, copy it to another disk while still in EXEC mode.

For more information, see "Managing Configuration History and Rollback" in the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

Step 2 

Place both the DSC and standby DSC in ROM Monitor mode.

Places the PRPs in ROM Monitor mode.

See Resetting the Configuration Register and Reloading a DSC to ROM Monitor Mode for more information.

Step 3 

Configure Boothelper for network access.

Enables network access for the PRP in preparation for downloading the new software.

Step 4 

set

Example:

rommon1> set

Displays the ROM Monitor environment variables.

Step 5 

unset BOOT

Example:

rommon2> unset BOOT

Clears the setting for the BOOT variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 6 

unset TFTP_FILE

Example:

rommon3> unset TFTP_FILE

Clears the setting for the TFTP_FILE variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 7 

unset CONFIG_FILE

Example:

rommon4> unset CONFIG_FILE

Clears the setting for the CONFIG_FILE variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 8 

TURBOBOOT=on, boot-device, options

Example:

rommon5> TURBOBOOT=on,disk0,format

Sets the Turboboot parameters.

Separate each parameter with a comma (,).

To enable the Turboboot process, specify on.

Specify a boot device where all software will be installed on the DSC and all DSDRSCs. We recommend disk0:.

To replace the existing software without formatting the boot device, replace options with clean.

To replace the existing software and format the boot device, replace options with format.

The default option is clean.

Any existing configuration is preserved.

Step 9 

sync

Example:

rommon6> sync

Saves the new ROM Monitor variable settings.

Step 10 

boot tftp://server/directory/filename

Example:

rommon7> boot 
tftp://223.255.254.254/softdir/c12k-mini.vm-3.4.
0

Retrieves the file from the TFTP server and installs it on the boot device.

Execute this command on the active PRP and specify the vm installation file from the TFTP server.

This process removes any existing software packages, resets the configuration register to 0x2, and boots the system.

Allow the system to fully boot. The "Press RETURN to get started" message appears twice. The first occurrence appears when the software is loaded into memory. The second occurrence happens after the software has been installed on the disk.

The system is fully booted when the following message appears:

SYSTEM CONFIGURATION COMPLETED
 
        

Do not wait for this step to complete before starting the next step.

Step 11 

Boot all non-DSC PRPs with the MBI.

Prepares PRPs to communicate with the DSC.

For instructions on booting the non-DSC PRPs with the MBI, see the "Bringing Up Non-DSC PRPs on Cisco XR 12000 Series Routers" section.

If the PRP is in a redundancy slot that is paired with an active PRP, the PRP starts as the standby for that PRP. The adjacent redundancy slots are as follows:

Slot 0 and Slot 1

Slot 2 and Slot 3

Slot 4 and Slot 5

Slot 6 and Slot 7

Slot 8 and Slot 9

Slot 10 and Slot 11

Slot 12 and Slot 13

Slot 14 and Slot 15

If the PRP is not in a redundancy slot that is paired with an active PRP, the PRP becomes available for assignment to SDRs.

Redundancy slot pairs are described in the "Managing the Router Hardware" chapter of Cisco IOS XR Getting Started Guide.

Examples

Setting the TURBOBOOT Variable

The following example shows how to set the TURBOBOOT variable on the DSC and save the change:

rommon1> TURBOBOOT=on,disk0,format
rommon2> sync
 
   

Booting the vm Installation File

The following example shows how to boot the DSC using the specified vm file on the specified TFTP server:

 
   
rommon 2> boot tftp://10.10.10.10/software/c12k-mini.vm-3.4.0
 
   
.
.
.
 
   
bios con0/RP1/CPU0 is now available
 
   
 
   
 
   
Press RETURN to get started.

Reinstalling to a Cisco XR 12000 Series Router from an Image on a Local Storage Device

This section describes the tasks required to install the Cisco IOS XR software on the boot device (such as disk0) using a vm image stored on a a local flash storage device (such as disk1). Complete the procedures exactly as described in this section.


Note Before booting begins, a delay of 10 minutes or more may occur while the vm image is read to memory from the removable flash disk1.


Prerequisites

A valid vm image, as described in the "Locating Installable Files" section, must be located on flash disk (disk1).

If this file is not present on disk1 or a different version is required, use one of the following options:

While the router is still in EXEC mode, copy the necessary vm image from a TFTP, an FTP, or an rcp server to the local storage device. We recommend flash disk1. This process is described in the the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide.

Consult your system administrator for a flash disk containing the bootable vm file.

Consult your Cisco representative for a flash disk containing the bootable vm file. See Obtaining Additional Publications and Information for more information.


Note We recommend the removable flash disk disk1 to store archives of vm and PIE files. The disk used to store the installable files cannot be used as a destination for installed software or configurations. Only the boot device can be used to store active software and configurations. See About the Boot Device (Destination Disk) for more information. See also the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide for more information.


The following hardware and software are required:

ROM Monitor 1.14 or higher

Boothelper c12kprp-boot-mz.120-32.S3

256 MB or higher flash disk0.

SUMMARY STEPS

1. Back up the router configuration while still in EXEC mode.

2. Copy the required vm file to the DSC flash disk that will store the files. We recommend the use of flash disk1. You can also use a flash disk that already has the correct image.

3. Place both the DSC and standby DSC in ROM Monitor mode.

4. set

5. unset BOOT

6. unset TFTP_FILE

7. unset CONFIG_FILE

8. TURBOBOOT=on, boot-device, options

9. sync

10. boot disk1:/filename

11. Boot all non-DSC PRPs with the MBI.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Back up the router configuration while still in EXEC mode.

(Optional) To preserve the current router configuration, copy it to another disk while still in EXEC mode.

See "Managing Configuration History and Rollback" in Cisco IOS XR Getting Started Guide for more information.

Step 2 

Copy the required vm file to the DSC local storage device (such as flash disk1). Or insert a flash disk that has the correct image.

Places the software on the router in preparation for installation.

For more information, see the "Prerequisites" section for this procedure.

Step 3 

Place both the DSC and standby DSC in ROM Monitor mode.

See Resetting the Configuration Register and Reloading a DSC to ROM Monitor Mode for more information.

Step 4 

set

Example:

rommon1> set

Displays the ROM Monitor environment variables.

Step 5 

unset BOOT

Example:

rommon2> unset BOOT

Clears the setting for the BOOT variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 6 

unset TFTP_FILE

Example:

rommon3> unset TFTP_FILE

Clears the setting for the TFTP_FILE variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 7 

unset CONFIG_FILE

Example:

rommon4> unset CONFIG_FILE

Clears the setting for the CONFIG_FILE variable.

This step is not required if the set command display shows that no value is assigned to this variable.

Step 8 

TURBOBOOT=on, boot-device, options

Example:

rommon5> TURBOBOOT=on,disk0,format

Sets the TURBOBOOT parameters.

Separate each parameter with a comma (,).

To enable the Turboboot process, specify on.

Specify a boot device where all software will be installed on the DSC and all DSDRSCs. We recommend disk0:.

To replace the existing software without formatting the boot device, replace options with clean.

To replace the existing software and format the boot device, replace options with format.

The default option is clean.

Any existing configuration is preserved.

Step 9 

sync

Example:

rommon6> sync

Saves the new ROM Monitor variable settings.

Step 10 

boot device:/filename

Example:

rommon7> boot disk1:/c12k-mini.vm-3.4.0
 
        

Boots the file located on the local storage device and and installs it to the boot device.

This process removes any existing software packages, resets the configuration register to 0x2, and boots the system.

Allow the system to fully boot. The "Press RETURN to get started" message appears twice. The first occurrence appears when the software is loaded into memory. The second occurrence happens after the software has been installed on the disk.

The system is fully booted when the following message appears:

SYSTEM CONFIGURATION COMPLETED
 
        

Note A delay of 10 minutes or more occurs while the software is read from the flash disk.

Step 11 

Boot all non-DSC PRPs with the MBI.

Prepares PRPs to communicate with the DSC.

For instructions on booting the non-DSC PRPs with the MBI, see the "Bringing Up Non-DSC PRPs on Cisco XR 12000 Series Routers" section.

If the PRP is in a redundancy slot that is paired with an active PRP, the PRP starts as the standby for that PRP. The adjacent redundancy slots are as follows:

Slot 0 and Slot 1

Slot 2 and Slot 3

Slot 4 and Slot 5

Slot 6 and Slot 7

Slot 8 and Slot 9

Slot 10 and Slot 11

Slot 12 and Slot 13

Slot 14 and Slot 15

If the PRP is not in a redundancy slot that is paired with an active PRP, the PRP becomes available for assignment to SDRs.

Redundancy slot pairs are described in "Managing the Router Hardware" in Cisco IOS XR Getting Started Guide.

Examples

Setting the TURBOBOOT Variable

The following example shows how to set the TURBOBOOT variable on the DSC and save the change:

rommon2> TURBOBOOT=on,disk0,format
rommon3> sync

Booting the vm Installation File

The following example shows how to boot the DSC using the specified vm file on flash disk1:

rommon4> boot disk1:/c12k-mini.vm-3.4.0

What to Do Next

After the system is up, it is in normal EXEC mode, and you can execute the full range of CLI commands.


Note If there was no previous router configuration, you must enter a root-system username and password when the boot process is complete.


After reinstalling the software, you might want to refer to the following additional instructions:

1. See "Verifying the System Interfaces" in Cisco IOS XR Getting Started Guide for instructions to verify that the interfaces are up and properly configured.

2. Install additional software from the PIE files, as necessary. See the "Upgrading and Managing Cisco IOS XR Software" chapter of Cisco IOS XR Getting Started Guide for more information.

3. See Obtaining Additional Publications and Information for a list of the additional documentation required to fully configure the router.

Bringing Up Non-DSC PRPs on Cisco XR 12000 Series Routers

If the Cisco IOS XR software has not been previously installed on a PRP and the PRP is installed in a Cisco XR 12000 Series Router, the card state shown by the show platform command is "Card Present." To bring up the card for use in the router, you must first install the minimum boot image (MBI) software on the card. This section describes how to install the MBI on non-DSC RPs.

Prerequisites

The following hardware and software are required:

ROM Monitor 1.14 or later

Boothelper c12kprp-boot-mz.120-32.S3

256 MB or higher flash disk0

Before you begin, collect the following information.

IP address of the TFTP server from which the software will be downloaded

The filename and directory of the MBI file that will be installed on the PRP

SUMMARY STEPS

1. Restart the PRP in ROM Monitor mode.

2. set

3. unset TURBOBOOT

4. unset BOOT

5. sync

6. boot tftp://server/path/mbiprp-rp.vm

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Restart the PRP in ROM Monitor mode.

Restarts the PRP in ROM Monitor mode.

If the rommon prompt appears, the PRP is already in ROM Monitor mode.

If the boot prompt appears, the PRP is in Boothelper. For information on starting ROM Monitor from this point, see the "Exiting Boothelper and Starting ROM Monitor" section.

Step 2 

set

Example:

rommon 1 > set

Displays the current setting of the ROM Monitor environment variables.

Step 3 

unset TURBOBOOT

Example:

rommon 2 > unset TURBOBOOT

Clears any value assigned to the TURBOBOOT variable.

If the TURBOBOOT variable displays no value in Step 2, you can skip this step.

Step 4 

unset BOOT

Example:

rommon 3 > unset BOOT

Clears the setting of the BOOT environment variable.

If the BOOT variable displays no value in Step 2, you can skip this step.

Step 5 

sync

Example:

rommon 4 > sync

Saves any configuration changes you have made to the environment variables.

Step 6 

boot tftp://server/path/mbiprp-rp.vm

Example:

rommon 5 > boot tftp://server1/path/mbiprp-rp.vm

Boots the MBI software.

For more information on the MBI software and locating the MBI, see the "Locating Installable Files" section.

When the MBI is loaded, the show platform command displays the state as "MBI Running."

If the PRP is in a redundancy slot that is paired with a DSC or DSDRSC, the PRP synchronizes the configuration with the active PRP, and this takes some time. When the synchronization is complete, the show platform command displays the state as "IOS-XR RUN."

Redundancy slot pairs are described in the "Managing the Router Hardware" chapter of Cisco IOS XR Getting Started Guide.

Examples

The following example is provided:

Bringing Up a Non-DSC RP

Bringing Up a Non-DSC RP

The following example shows how to bring up a non-DSC RP with the MBI:

rommon 1 > set
PS1=rommon ! > 
IP_SUBNET_MASK=
TFTP_SERVER=
DEFAULT_GATEWAY=
IP_ADDRESS=
RET_2_RUTC=
IOX_ADMIN_CONFIG_FILE=
CONFIG_FILE=
BOOTLDR=
CONFGEN=
CHASSIS_SN=TBA07280054
IOX_CONFIG_FILE=
AUX_AUTHEN_LEVEL=0
TURBOBOOT=on,disk0,format
ReloadReason=79
BSI=0
RET_2_RCALTS=
BOOT=tftp://server1/path/file
 
   
rommon 2 > unset TURBOBOOT
 
   
rommon 3 > unset BOOT
 
   
rommon 4 > sync
 
   
rommon 5 > boot tftp://server1/path/mbiprp-rp.vm
 
   
Self decompressing the image : BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB [OK]
 
   
Loading path/mbiprp-rp.vm from server1 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 8726056 bytes]
Zø####################################################################
System page at phys:00023000 user:00023000 kern:00023000
Starting next program at v0022a188
 
   
Restricted Rights Legend
 
   
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
 
   
           Cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
 
   
Cisco IOS XR Software for the Cisco XR c12000-mbiprp,
Copyright (c) 2006 by Cisco Systems, Inc.