ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2 · ROM...

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers,IOS XR Release 5.2.xFirst Published: 2014-07-01

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-32691-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2014 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarkshttp://www.cisco.com/go/trademarks

C O N T E N T S

P r e f a c e Preface vii

Changes to This Document vii

Obtaining Documentation and Submitting a Service Request vii

C H A P T E R 1 New and Changed ROMMON Features 1

New and Changed ROMMON Feature Information 1

C H A P T E R 2 ROMMonitor Overview 3

Information About ROM Monitor 3

Entering ROM Monitor Mode 5

Prerequisites 5

Resetting the Configuration Register and Reloading a RSP Card to ROM Monitor Mode 6

Verifying the Router State: Example 8

Placing the RSP Cards in ROM Monitor Mode: Example 8

Manually Halting the Initialization Process During System Reload 9

ROMMonitor Commands 9

Commonly Used ROMMonitor Commands 9

Displaying the Available ROM Monitor Commands 11

Displaying the Available ROM Monitor Commands: Examples 11

Changing the ROM Monitor Prompt 12

Displaying the Configuration Register Setting 12

Environment Variables 12

Frequently Used Environmental Variables 13

Displaying Environment Variable Settings 14

Entering Environment Variable Settings 15

Saving Environment Variable Settings 15

Clearing Environment Variable Settings 15

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.x OL-32691-01 iii

Viewing Chassis Serial Numbers 15

Exiting ROM Monitor Mode 16

Resetting the Configuration Register Using Prompts 16

Resetting to EXEC Mode or MBI Validation Mode 17

Exiting ROM Monitor Mode: Examples 17

Attaching to Primary RSP from Standby RSP 18

Additional References 19

C H A P T E R 3 Router Recovery with ROMMonitor 21

Information About Router Recovery 21

About ROMMON Installation Files 22

Locating Installable Files 22

tar Filenames and Version Numbers 23

vm Filenames and Version Numbers 24

About the TURBOBOOT Variable 25

About the Boot Device (Destination Disk) 26

Reinstalling Cisco IOS XR Software on Cisco ASR 9000 Series Router 27

Cisco ASR 9000 Series Router Router Installation Overview 27

Installation from a TFTP Server 27

Reinstalling to a CiscoASR 9000 SeriesRouter from a TFTP Server Image 28

Reinstalling to a Cisco ASR 9000 Series Router from a TFTP Server Image 29

Reinstalling to a Cisco ASR 9000 Series Router from a TFTP Server Image:

Example 33

Installing Cisco IOS XR Software on Cisco ASR 9000 Series Router from a USB

Drive 34

What to Do Next 36


Related Documents 37

Technical Assistance 38

C H A P T E R 4 Managing Configuration Files in ROMMonitor 39

Information about Configuration Files 39

Specifying an Alternative Administration Configuration 40

Specifying a Temporary Alternative Administrative Configuration with the -o Boot

Option 40

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.xiv OL-32691-01

Contents

Specifying a Permanent Alternative Administrative Configuration File with the

IOX_ADMIN_CONFIG_FILE= Variable 43

Specifying an Alternative SDR Configuration 46

Specifying a Temporary SDR Configuration File with the -a Boot Option 47

Specifying a Permanent SDR Configuration File with the IOX_CONFIG_FILE= Variable 50

Specifying an Alternate Storage Location for Configuration Files 53


C H A P T E R 5 Password Recovery in ROMMonitor Mode 57

Information About Password Recovery 57

Recovering the Root Password on Single-RSP Routers 57

Recovering the Root Password on Redundant-RSP Routers 59

Bypassing ksh Authentication 60


C H A P T E R 6 Upgrading and Downgrading ROMMonitor Firmware 63

Information About ROM Monitor Firmware 63

ROMMON A and ROMMON B 64

Upgrading or Downgrading a Single Node or All Nodes 64

Reloading Nodes After a ROMMON Firmware Change 64

Upgrading or Downgrading ROM Monitor Using the FPD PIE 65

Troubleshooting Tips 68

ROMMonitor Upgrades: Examples 69

ROMMonitor Upgrade: Example 69

Graceful Reload of a Cisco ASR 9000 Series Router: Example 72


C H A P T E R 7 Image Refresh Using the Archive and Restore Feature 77

Information About Image Refresh 77

Prerequisites 78

Archiving Cisco IOS XR Image on a Local Disk 78

Archiving Cisco IOS XR Image on a Local Disk: Example 79

Restoring Cisco IOS XR Image from the local device 80

Restoring Cisco IOS XR Image from the Local Device: Example 82

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.x OL-32691-01 v

Contents

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.xvi OL-32691-01

Contents

Preface

From Release 6.1.2 onwards, Cisco introduces support for the 64-bit Linux-based IOS XR operating system.Extensive feature parity is maintained between the 32-bit and 64-bit environments. Unless explicitly markedotherwise, the contents of this document are applicable for both the environments. For more details on CiscoIOS XR 64 bit, refer to the Release Notes for Cisco ASR 9000 Series Routers, Release 6.1.2 document.

The Cisco ASR 9000 Series Aggregation Services Router ROM Monitor Guide preface contains thesesections:

• Changes to This Document, page vii

• Obtaining Documentation and Submitting a Service Request, page vii

Changes to This DocumentThis table lists the technical changes made to this document since it was first printed.

Change SummaryDateRevision

Initial release of this document.July 2014OL-32691-01

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What'sNew in Cisco Product Documentation RSS feed. RSS feeds are a free service.

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.x OL-32691-01 vii

http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xr-software/products-release-notes-list.htmlhttp://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/assets/cdc_content_elements/rss/whats_new/whatsnew_rss_feed.xmlhttp://www.cisco.com/assets/cdc_content_elements/rss/whats_new/whatsnew_rss_feed.xml

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.xviii OL-32691-01

PrefaceObtaining Documentation and Submitting a Service Request

C H A P T E R 1New and Changed ROMMON Features

This table summarizes the new and changed feature information for the Cisco ASR 9000 Series AggregationServices Router ROM Monitor Guide, and tells you where they are documented.

• New and Changed ROMMON Feature Information, page 1

New and Changed ROMMON Feature InformationWhere DocumentedChanged in ReleaseDescriptionFeature

Upgrading and DowngradingROM Monitor Firmwarechapter:

• Information About ROMMonitor Firmware , onpage 63

Refer Software/FirmwareCompatibility Matrixinformation at http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html link, for details ofminimum ROMMONrequirements.

Release 5.2.0Minimum ROMMON versionfor ASR9001 is 2.04

ROMMON version forASR9001

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.x OL-32691-01 1

http://www.cisco.com/web/Cisco_IOS_XR_Software/index.htmlhttp://www.cisco.com/web/Cisco_IOS_XR_Software/index.htmlhttp://www.cisco.com/web/Cisco_IOS_XR_Software/index.htmlhttp://www.cisco.com/web/Cisco_IOS_XR_Software/index.html

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2.x2 OL-32691-01

New and Changed ROMMON FeaturesNew and Changed ROMMON Feature Information

C H A P T E R 2ROM Monitor Overview

This chapter provides an overview of ROM Monitor concepts and operations. For instructions on how toperform various tasks in ROM Monitor (ROMMON) mode, see the other chapters in this book.

This chapter includes these main topics:

• Information About ROM Monitor, page 3

• Entering ROM Monitor Mode, page 5

• ROMMonitor Commands, page 9

• Displaying the Configuration Register Setting, page 12

• Environment Variables, page 12

• Viewing Chassis Serial Numbers, page 15

• Exiting ROM Monitor Mode, page 16

• Attaching to Primary RSP from Standby RSP, page 18

• Additional References, page 19

Information About ROM MonitorThe ROMMonitor is a bootstrap program that initializes the ASR 9000 hardware and boots the Cisco IOSXR software when you power on or reload a router. A version of the ROM Monitor software exists on eachcard and is factory supplied. The ROM Monitor program provides an initial power-on environment for eachcard. If the Cisco IOS XR software is rebooted or unable to run, the corresponding card returns to the ROMMonitor mode.

When you connect a terminal to a card that is in the ROM Monitor mode, the ROM Monitor CLI prompt isdisplayed.

Cisco ASR 9000 Series Router Prompt

rommon B1>


The ROMMonitor software is known by many names. It is sometimes called ROMMON because of the CLIprompt in ROM Monitor mode. The ROM Monitor software is also called the boot software, boot image, orboot helper.

Although it is distributed with routers that use the Cisco IOSXR software, ROMMonitor is a separate programfrom the Cisco IOS XR software. During normal startup, the ROM Monitor initializes the cards, and thencontrol passes to the Cisco IOS XR software. After the Cisco IOS XR software takes over, ROM Monitor isno longer in use.

Understanding the Role of the Route Switch Processor (RSP) Card

The Cisco ASR 9000 Series Router contains series of chassis slots, each of which can hold one of severaltypes of line cards (LCs). Two slots in the chassis are reserved for route switch processors (RSP) cards thatprovide the central point for chassis provisioning and management.

The active RSP for the owner SDR is called the Designated Shelf Controller (DSC). This card performssystem-wide functions. If the active RSP card is placed in ROM Monitor mode, it is no longer running theCisco IOSXR software. If a standby RSP card is available, then the standby RSP card resumes router operations.If both the RSP cards are not available or if the active RSP (previously standby) is also placed in the ROMMonitor mode, router operations will stop.

Designated Secure Domain Router Shelf Controller (DSDRSC)

When the Designated Secure Domain Router Shelf Controller (DSDRSC) in an SDR is placed in ROMMonitormode, the router operations are transferred to the standby DSDRSC (if available). If both the primary andstandby DSDRSCs are in ROM Monitor mode, then the router operations cease because theCisco IOS XR software is no longer running.

Accessing ROM Monitor Mode on the RSP Card

In most situations, you interact with the ROM Monitor mode only on the RSP cards. The active RSP cardcontains the administration configuration for the entire system and distributes the required software to all theother nodes in the router. All the tasks in this document describe ROM Monitor mode accessed through theRSP card for the system.

The line cards have its own ROMMonitor software which can be upgraded using the RSP FPD upgradeoperation, if required.

Environmental Variables and the Configuration Register

Two primary connections exist between ROMMonitor and the Cisco IOS XR software: the ROM Monitorenvironment variables and the configuration register.

The ROMMonitor environment variables define the location of the Cisco IOS XR software and describe howto load it. After ROM Monitor has initialized the card, it uses the environment variables to locate and loadthe Cisco IOS XR software. The common environment variables are BOOT, IP_ADDRESS,DEFAULT_GATEWAY, TFTP_FILE, TURBOBOOT and SUBNET_MASK.

The configuration register is a software setting that controls how a card starts up. One of the primary uses ofthe configuration register is to control whether the card starts in ROMMonitor mode or Administration EXECmode. The configuration register is set in either ROMMonitor mode or Administration EXECmode as needed.Typically, you set the configuration register using the Cisco IOS XR software prompt on the active RSP whenyou need to use ROMMonitor mode. When the maintenance in ROMMonitor mode is complete, you changethe configuration register so the card reboots with the Cisco IOS XR software.


ROM Monitor OverviewInformation About ROM Monitor

Throughout this guide, the term RSP is used to refer to the RSP cards supported onCisco ASR 9000 Series Routers. If a feature or an issue applies to only one platform, the accompanyingtext specifies the platform.

Note

Accessing ROM Monitor Mode with a Terminal Connection

When an RSP is in ROM Monitor mode, you can access the ROM Monitor software only from a terminalconnected directly to the console port of the card. Because the Cisco IOS XR software (EXEC mode) is notoperating, the nonmanagement interfaces (such as GigabitEthernet interfaces) are not accessible. Basically,all Cisco IOS XR software resources are unavailable. The hardware is there, but no configuration exists tomake use of the hardware.

Network Management Access and ROM Monitor Mode

Some people get confused when they start to use ROMMonitor mode. It is important to remember that ROMMonitor mode is a router mode, not a mode within the Cisco IOS XR software. It is best to remember thatROMMonitor software and the Cisco IOSXR software are two separate programs that run on the same router.At any given time, the router is running one of these programs, but it never runs both at the same time.

One area that can be confusing when using ROM Monitor and the Cisco IOS XR software is the area thatdefines the IP configuration for the Management Ethernet interface. Most router users get comfortable withconfiguring the Management Ethernet interface in the Cisco IOS XR software. When the router is in ROMMonitor mode, however, the router is not running the Cisco IOS XR software, so that Management Ethernetinterface configuration is not available.

To access other devices, such as a TFTP server, while in ROM Monitor mode on theCisco ASR 9000 Series Router, you must configure the ROM Monitor variables with IP access information.

Entering ROM Monitor ModeThe following sections describe two ways to enter ROM Monitor mode:

PrerequisitesBefore you place a RSP card in ROM Monitor mode, verify that the system is in a steady state:

1 Prepare the RSP card:

• Anticipate substantial downtime, including the loss of packet forwarding on the system.

• Verify the sanity of the configuration file system using the cfs check command in EXEC mode.

• Verify that all changes to the active router configuration are saved with the commit command inany configuration mode.

• Verify that all changes to the active software set are saved with the install commit command inAdministration EXEC mode.

• Verify that all install commit processes are complete with the show install committed command inAdministration EXEC mode. This command displays the committed packages that become active


ROM Monitor OverviewEntering ROM Monitor Mode

during the next router boot. If any of the processes are not committed, use the install commitcommand in the Administration mode.

2 Verify that the other nodes in the system are in a steady state:

• If a standby RSP is installed, verify that it is in the ready state with the show redundancy commandin EXEC mode.

• Verify that all available nodes in the system are in IOS XR RUN state with the show platformcommand in EXEC mode.

After you have verified that the system is in a stable state, you can enter ROM Monitor mode by setting theconfiguration register setting and entering the reload command, as described in the following steps:

Resetting the Configuration Register and Reloading a RSP Card to ROM MonitorMode

In normal operating conditions, it should not be necessary to use ROM Monitor mode. If you do find itnecessary to place a RSP card in ROMMonitor mode, make sure that the system is in a steady state and thatyou are prepared for the consequences of a system reload.

SUMMARY STEPS

1. Verify the router is in a steady state.2. Connect a terminal to the RSP card console port and log in to the router.3. admin4. config-register boot-mode rom-monitor location command, exit command and reload command

or config-register boot-mode rom-monitor location all command and reload location all command.

DETAILED STEPS

PurposeCommand or Action

Ensures that all configurations are saved and that noinstallation processes are running.

Verify the router is in a steady state.Step 1

Connects a terminal or PC to the RSP card console portand establishes a router management session.

Connect a terminal to the RSP card console port and log in to therouter.

Step 2

For more information on connecting a terminal, seeConnecting and Communicating with the Router inCisco ASR 9000 Series Aggregation Services RouterGetting Started Guide.

Enters administration EXEC mode.admin

Example:RP/0/RSP0/CPU0:router# admin

Step 3


ROM Monitor OverviewResetting the Configuration Register and Reloading a RSP Card to ROM Monitor Mode


config-register boot-mode rom-monitor location command,exit command and reload command or

Step 4 • Enter the following commands to place only oneRSP card (active or standby) in ROM Monitormode:config-register boot-mode rom-monitor location all command and

reload location all command. • Enter the boot-mode rom-monitor location command, where is the ID

Example:RP/0/RSP0/CPU0:router(admin)#config-register boot-mode rom-monitor location 0/RSP0/CPU0

of the card, to set the configuration register forROMMonitor mode during the next card reload.

• Enter the exit command to exit administrationEXEC mode.

RP/0/RSP0/CPU0:router(admin)# exitRP/0/RSP0/CPU0:router# reloadOr,RP/0/RSP0/CPU0:router(admin)# config-register boot-mode • Enter the reload command to reload the card and

enter ROM Monitor mode.rom-monitorlocation allRP/0/RSP0/CPU0:router(admin)# reload location all

Note • If you specify the config-registerboot-mode rom-monitorcommand without the locationkeyword, then all the RSPs areplaced in ROM Monitor mode.

• Enter the following commands to place all RSPsin ROM Monitor mode:

• Enter the config-register boot-mode rom-monitorlocation all command to reset the configurationregister for all RSPs in the system.

• Enter the reload location all command inadministration EXEC mode to reload all RSPs inthe system.

Make sure you have access to the console portsof both RSP0 and RSP1 cards on the system.To enter the system to the ROM Monitormode, pressCtrl-C a few times on both RSP0and RSP1 consoles until you get to the ROMMonitor mode.

Note

Resetting the configuration register maychange the baud rate for the console. Thedefault baud rate is 9600.

Caution

To verify the configuration register setting, enterthe show variables boot command in theadministration EXEC mode.

Tip



Verifying the Router State: ExampleThe following example shows the redundancy roles of both RSPs and shows that both are operating inIOS XR RUN state:

RP/0/RSP0/CPU0:router#show redundancy

Wed Jun 30 21:35:23.656 UTCRedundancy information for node 0/RSP0/CPU0:==========================================Node 0/RSP0/CPU0 is in ACTIVE rolePartner node (0/RSP1/CPU0) is in STANDBY roleStandby node in 0/RSP1/CPU0 is readyStandby node in 0/RSP1/CPU0 is NSR-ready

Reload and boot info----------------------A9K-RSP-8G reloaded Tue Jun 29 18:56:15 2010: 1 day, 2 hours, 39 minutes agoActive node booted Tue Jun 29 18:56:15 2010: 1 day, 2 hours, 39 minutes agoStandby node boot Tue Jun 29 18:55:54 2010: 1 day, 2 hours, 39 minutes agoStandby node last went not ready Tue Jun 29 18:58:52 2010: 1 day, 2 hours, 36minutes agoStandby node last went ready Tue Jun 29 18:59:52 2010: 1 day, 2 hours, 35 minutesagoThere have been 0 switch-overs since reload

Active node reload "Cause: Node reload is required by install operation"Standby node reload "Cause: pID node reload is required by install operation"

RP/0/RSP0/CPU0:router#show redundancy summaryWed Jun 30 21:35:32.259 UTC

Active Node Standby Node----------- ------------0/RSP0/CPU0 0/RSP1/CPU0 (Ready, NSR: Ready)

RP/0/RSP0/CPU0:router#show platform

Wed Jun 30 21:35:35.944 UTCNode Type State Config State-----------------------------------------------------------------------------0/RSP0/CPU0 A9K-RSP-8G(Active) IOS XR RUN PWR,NSHUT,MON0/RSP1/CPU0 A9K-RSP-8G(Standby) IOS XR RUN PWR,NSHUT,MON0/1/CPU0 A9K-8T-E IOS XR RUN PWR,NSHUT,MON0/5/CPU0 A9K-40GE-B IOS XR RUN PWR,NSHUT,MON0/6/CPU0 A9K-2T20GE-E IOS XR RUN PWR,NSHUT,MON

Placing the RSP Cards in ROM Monitor Mode: ExampleThe following example shows how to place the RSP in the ROM Monitor mode:

RP/0/RSP0/CPU0:router# adminRP/0/RSP0/CPU0:router(admin)# config-register boot-mode rom-monitor location all

Set to rom-monitor mode for all mgmt nodes:RP/0/RSP0/CPU0:router(admin)#config-register boot-mode rom-monitor location allSuccessfully set config-register to RP/0/RSP0/CPU0:routerSuccessfully set config-register to RP/0/RSP0/CPU0:router



Manually Halting the Initialization Process During System ReloadTo force the RSP card to stop loading and enter ROMMonitor mode, press Ctrl-C when you see the followingmessage:

MBI validation sending request.HIT Ctrl-C to abortTYPE 'Send Break'to abortThis message usually appears during the first 20 seconds of system startup. Press the Ctrl-C key combinationimmediately. It may be necessary to press the Ctrl-C keys repeatedly during this time to ensure that theinitialization process stops and the system enters ROM Monitor mode. This ends your Telnet session to theconsole or auxiliary port.

This operation can be performed only from a terminal directly connected to the RSP card console port. Formore information, see the “Connecting and Communicating with the Router” section in Cisco ASR 9000 SeriesAggregation Services Router Getting Started Guide.

When the RSP card is placed in ROMMON, it switches over to the standby RSP card, which can thenalso be placed in ROMMON. Repeat this process for both RSP cards.

Note

ROM Monitor CommandsThe commands in the ROM Monitor mode are different from those available in the Cisco IOS XR software.You can run ROM Monitor commands only while in ROM Monitor mode, and you cannot runCisco IOS XR software commands. This section includes the following topics:

Commonly Used ROM Monitor CommandsThe table below summarizes the commands commonly used in ROM Monitor. For specific instructions onusing these commands, refer to the relevant procedure in this document.

Table 1: Commonly Used ROM Monitor Commands

DescriptionROMMON Command

Manually boots a vm Cisco IOS XR softwareimage.

boot image

Manually boots the Cisco IOS XR softwarewith a temporary alternative administrationconfiguration file.

boot image –o config-file-path


ROM Monitor OverviewManually Halting the Initialization Process During System Reload

DescriptionROMMON Command

Manually boots the Cisco IOS XR softwarewith a temporary default SDR configurationfile. The system can also be booted fromexternal compactflash usingCiscoASR 9000 Series Router Image Refreshmethod.

boot tftp://config-file-path/image

Displays the system cookie.cookie

Changes the config-register setting.

When the value of confreg is 0, itmeans autoboot is disabled and youneed to manually boot theCisco IOS XR software image fromthe ROM Monitor mode. However,if the value of confreg is non-zerovalue of 0x2, it means autoboot isenabled and the ROMMonitor modeautomatically boots theCisco IOS XR software image givenin the BOOT= environment variable.

Note

confreg

Displays the available local storage devices(for example, disk0: and disk1:).

dev

Displays the files on a storage device.dir

Displays the chassis serial number, MACaddress, MAC range, PID, Controller type,version, and so on, in aCisco ASR 9000 Series Router.

bpcookie

Resets the node.reset

Displays the currently set ROM Monitorenvironmental settings.

set

Saves the new ROMMonitor environmentalsettings.

sync

Removes an environmental variable setting.unset

Displays the ROM Monitor version.version


ROM Monitor OverviewCommonly Used ROM Monitor Commands

Displaying the Available ROM Monitor CommandsThe table below describes the available help commands for ROM Monitor mode.

Table 2: Help Commands in ROMMON

Description

Displays a summary of all available ROMMonitor commands.

help or ?

Displays information about command syntax.-?

Commands are case sensitive. You can halt any command by pressing Ctrl-C.Note

Displaying the Available ROM Monitor Commands: ExamplesThe following example showswhat appears when you enter the ? command on a CiscoASR 9000 Series Router:

rommon B1> ?alias set and display aliases commandboot boot up an external processbpcookie display the backplane cookiecbcinfo Display information from CBCcbcmsg Send a message to the CBCcbcping Send "PING" to CBC LED Matrixclocks get CPU clock informationconfreg configuration register utilitycookie display the system cookiedev list the device tabledir list files in file systemdimminfo Display info for DDR DIMMsdis disassemble instruction streamdnld serial download a program moduledump display a block of memoryddump display a block of memory as double wordsdumpspd display DDR2 SPD informationfpgainfo display information about FPGA imagesftcookie display the fan tray cookiehelp monitor builtin command helphistory monitor command historymeminfo main memory informationportstatus Show 6 port switch port statusrepeat repeat a monitor commandreset system resetshowrobfl show run logsrominfo display the ROMMON header informationscanpci1 scan for devices on PCI bus 1scanpci2 scan for devices on PCI bus 2set display the monitor variablessync write monitor environment to NVRAMunalias unset an aliasunset unset a monitor variableversion display rommon software, board, version


ROM Monitor OverviewDisplaying the Available ROM Monitor Commands

The following example shows the parameters for the dir (directory) command:

rommon B1> dir -?bad device nameusage: dir The following example showswhat appears when you enter the version command at the CiscoASR 9000 SeriesRouter ROM Monitor mode prompt:

rommon B1 > version

System Bootstrap, Version 1.0(20081208:173612) [ASR9K ROMMON],Copyright (c) 1994-2008 by Cisco Systems, Inc.Compiled Mon 08-Dec-08 09:36 by abc

LNC2: 1.17 [00000001/00000011]TMPO: 1.13 [00000001/0000000d]LB_3: 1.14 [00000001/0000000e]PUNT: 1.4 [00000001/00000004]CBC: 1.1BID: 0x0004

Changing the ROM Monitor PromptYou can change the prompt in ROM Monitor mode by using the PS1= command as shown in the followingexample:

rommon B1> PS1= “ASR9K_ROMMON B1!>”

Changing the prompt is useful if you are working with multiple routers in ROM Monitor at the same time.This example specifies that the prompt is ASR9K_ROMMON B followed by the line number.

Displaying the Configuration Register SettingTo display the current configuration register setting, enter the confreg commandwithout parameters as follows:

rommon B1> confreg

Configuration Summary(Virtual Configuration Register: 0x1920)enabled are:console baud: 9600boot: the ROM Monitor

do you wish to change the configuration? y/n [n]:The configuration register setting is labeled Virtual Configuration Register. Enter the no command to avoidchanging the configuration register setting.

Environment VariablesThe ROMMonitor environment variables define the attributes of the ROM Monitor, such as the IP addressfor an RSP control Ethernet port or the location of the Cisco IOS XR software and describe how to load it.


ROM Monitor OverviewChanging the ROM Monitor Prompt

Environmental variables are entered like commands and are always followed by the equal sign (=). Environmentvariable settings are entered in capital letters, followed by a definition. For example:

TURBOBOOT=on,disk0,formatUnder normal operating conditions, you do not need to modify these variables. They are cleared or set onlywhen you need to make changes to the way ROMMonitor operates.

Before loading CISCO IOS XR software image in Cisco ASR 9000 Virtualized Service Module (VSM)Service Card, you must ensure that these environment variables are set at the LC ROMMON prompt:

Note

• TFTP_EXTERNAL_BOOT=0

• AUTOMATIC_BOOT=1

Frequently Used Environmental VariablesThe table below shows the main ROMMonitor environmental variables. For instructions on how to use thesevariables, see the relevant instructions in this document.

DescriptionEnvironmental variable

DescriptionTFTP_MGMT_INTF={0 | 1}

DescriptionIP_ADDRESS=ip_address

Sets the subnet mask for theManagement Ethernet interface onthe RSP card.

IP_SUBNET_MASK=ip_address

DescriptionDEFAULT_GATEWAY=ip_address

DescriptionTFTP_SERVER=ip_address

DescriptionTFTP_FILE=drive:path/file

Sets the subnet mask for theManagement Ethernet interface onthe RSP card.

TURBOBOOT=on, boot-device, options

Sets the default gateway that servesthe RSP card.

BOOT=drive:path/file


ROM Monitor OverviewFrequently Used Environmental Variables

DescriptionEnvironmental variable

Specifies the sequence of localstorage devices in which thedisk-boot operation occurs. (Forexample, the disk0:;disk1: sequenceindicates to boot from disk0: deviceinitially and if failure occurs, bootfrom the disk1: device.

BOOT_DEV_SEQ_OPER=drive:

Indicates the configured primaryand secondary devices (disk0: anddisk1:) for disk mirroring. Thisvariable is usually set byCisco IOS XR software.

BOOT_DEV_SEQ_CONF=drive:

Bypasses ksh authentication. Areboot is required only on the cardthat has to bypass authentication.

AUX_AUTHEN_LEVEL=number

Permanently changes the locationof the default administrationconfiguration file.

IOX_ADMIN_CONFIG_FILE= drive:path/file

Permanently changes the locationof the router configuration file.

IOX_CONFIG_FILE=drive:path/file

Permanently changes the defaultlocation where configuration filesare saved.

IOX_CONFIG_MEDIUM=drive:path

Sets to Y in Cisco IOSXR softwareto indicate disk mirroring isenabled. When it is set to N, itindicates disk mirroring is disabled.

MIRROR_ENABLE=value

Displaying Environment Variable SettingsTo display the current environment variable settings, enter the set command at the ROMMonitor mode prompt:

rommon B1> set

PS1=RO RSP P4D-17 ! >IP_ADDRESS=172.29.52.137DEFAULT_GATEWAY=172.29.52.1IP_SUBNET_MASK=255.255.255.0TFTP_SERVER=172.23.16.81IOX_ADMIN_CONFIG_FILE=TFTP_MGMT_INTF=0


ROM Monitor OverviewDisplaying Environment Variable Settings

BOOT_DEV_SEQ_CONF=disk0:;disk1:MIRROR_ENABLE=Y?=0TFTP_FILE=/auto/tftpboot-users/lpatton/comp-asr9k-mini.vm-5.2.0TURBOBOOT=BSI=0BOOT_DEV_SEQ_OPER=disk0:;disk1:BOOT=disk0:asr9k-os-mbi-5.2.0/mbiasr9k-rp.vm,1;ReloadReason=1asr9k-os-mbi-5.3.0

Entering Environment Variable SettingsEnvironment variable settings are entered in capital letters, followed by a definition. The following exampleshows the environmental variables used to configure the control Ethernet port on aCisco ASR 9000 Series Router:

rommon B1> IP_ADDRESS=1.1.1.1rommon B2> IP_SUBNET_MASK=255.255.254.0rommon B3> DEFAULT_GATEWAY=1.1.0.1

Saving Environment Variable SettingsTo save the current environment variable settings, enter the sync command:

rommon B1> sync

Environmental values that are not saved with the sync command are discarded whenever the system isreset or booted.

Note

Clearing Environment Variable SettingsTo clear the environment variable settings, enter the unset command:

rommon B1> unsetTo make the change permanent, use the sync command.

Environmental values that are not saved with the sync command are discarded whenever the system isreset or booted.

Note

Viewing Chassis Serial NumbersThe chassis serial number can be read from an RSP that is running in ROM Monitor mode. Viewing thechassis number from the RSP may be necessary if the physical label is missing or damaged.


ROM Monitor OverviewEntering Environment Variable Settings

1 Attach a console to the console port of an RSP SC or RP in the chassis. (Only the RSP card SC or RPneeds to run to perform this procedure. Other cards need not be inserted.)

2 Apply power to the chassis.

3 Enter ROM Monitor mode.

4 Enter the bpcookie command in privilege mode of the ROMMonitor prompt to display the chassis serialnumber.

5 Return the router to EXEC mode.

Exiting ROM Monitor ModeTo exit ROM Monitor mode, you must change the configuration register and reset the RSP.

Resetting the Configuration Register Using PromptsTo change the configuration register settings in the ROM Monitor mode, enter the confreg command at theROM Monitor mode. Entering this command displays the configuration summary and the prompts used tochange the configuration.

In ROM Monitor mode, you can change the configuration register value using the configuration registerprompts, as shown in this procedure.

SUMMARY STEPS

1. confreg2. Respond to each prompt as instructed.3. reset

DETAILED STEPS


Starts the configuration register configuration prompts.confreg

Example:

rommon B1> confreg

Step 1

See the example that follows this procedure for moreinformation.

Respond to each prompt as instructed.Step 2

Resets and initializes the router.reset

Example:

rommon B2> reset

Step 3


ROM Monitor OverviewExiting ROM Monitor Mode

Resetting to EXEC Mode or MBI Validation ModeTo exit the ROM Monitor mode and reset to EXEC mode, enter the confreg command at the ROM Monitormode prompt. Respond to prompts as instructed.

Exiting ROM Monitor Mode: ExamplesThe following example shows how to enable ROM Monitor mode at the next system boot:

rommon B5 > confreg

Configuration Summary(Virtual Configuration Register: 0x1920)

enabled are:console baud: 9600boot: the ROM Monitor

do you wish to change the configuration? y/n [n]: yenable "diagnostic mode"? y/n [n]: nchange console baud rate? y/n [n]: nchange the boot characteristics? y/n [n]: yenter boot type:0 = ROM Monitor2 = MBI Validation Boot Mode

[0]: 0



do you wish to change the configuration? y/n [n]: n

You must reset or power cycle for new config to take effectrommon B6 > resetThe following example shows how to enter the minimum boot image (MBI) validation mode or the EXECmode of Cisco IOS XR software at the next system boot:

rommon B7 > confreg



do you wish to change the configuration? y/n [n]: yenable "diagnostic mode"? y/n [n]: nchange console baud rate? y/n [n]: nchange the boot characteristics? y/n [n]: yenter boot type:0 = ROM Monitor2 = MBI Validation Boot Mode

[0]: 2

Configuration Summary


ROM Monitor OverviewResetting to EXEC Mode or MBI Validation Mode

(Virtual Configuration Register: 0x1922)enabled are:console baud: 9600boot: MBI Boot

do you wish to change the configuration? y/n [n]: n

You must reset or power cycle for new config to take effect

rommon B8 > resetTo reset to the MBI validation mode or EXEC mode, select 2 as the boot type. Enter the reset command toboot the RSP in the EXEC mode.

MBI validation mode causes the RSP to boot the startup Cisco IOS XR software and configuration.Note

Attaching to Primary RSP from Standby RSPYou must follow these steps in order to attach to the primary RSP from standby RSP:

• From the console port of the standby RSP, press the ESC key.

• Type ksh and press ENTER key.

• Login with a local username and password.

• Attach to the peer RSP using attach node command.

• Launch the console using /pkg/bin/exec -a command.

- - -- - -This (D)RP Node is not ready or active for login /configurationUsername: rootPassword:

# uname -aQNX node0_RSP0_CPU0 6.4.0 2014/01/07-14:26:36PST asr9k-rsp x86# attach 0/RSP1/CPU0

attach: Starting session 1 to node 0/RSP1/CPU0

# /pkg/bin/exec -a

RP/0/RSP1/CPU0#show platformMon Apr 21 16:00:37.573 UTCNode Type State Config State-----------------------------------------------------------------------------0/RSP0/CPU0 A9K-RSP880-SE(Standby) IOS XR RUN PWR,NSHUT,MON0/RSP1/CPU0 A9K-RSP880-SE(Active) IOS XR RUN PWR,NSHUT,MON0/1/CPU0 A9K-24x10GE-SE IOS XR RUN PWR,NSHUT,MON0/2/CPU0 A9K-SIP-700 IOS XR RUN PWR,NSHUT,MON0/2/1 SPA-8XOC3-POS OK PWR,NSHUT,MONRP/0/RSP1/CPU0#exitTerminating attach to node 0/RSP1/CPU0..


ROM Monitor OverviewAttaching to Primary RSP from Standby RSP

Additional ReferencesThe following sections provide references related to the ROM Monitor.

Related Documents

Document TitleRelated Topic

Connecting and Communicating with the Router inCisco ASR 9000 Series Aggregation Services Router GettingStarted Guide

Connecting a terminal to a router

Cisco IOS XR Software Documentation: http://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.html

Configuring a router with Cisco IOS XRsoftware

Technical Assistance

LinkDescription

http://www.cisco.com/supportThe Cisco Support website provides extensiveonline resources, including documentation andtools for troubleshooting and resolving technicalissues with Cisco products and technologies.

To receive security and technical informationabout your products, you can subscribe tovarious services, such as the Product Alert Tool(accessed from Field Notices), the CiscoTechnical Services Newsletter, and ReallySimple Syndication (RSS) Feeds.

Access to most tools on the Cisco Supportwebsite requires a Cisco.com user ID andpassword.


ROM Monitor OverviewAdditional References

http://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.htmlhttp://www.cisco.com/support


ROM Monitor OverviewAdditional References

C H A P T E R 3Router Recovery with ROM Monitor

This chapter describes the router recovery methods in ROM Monitor (ROMMON) mode of the router.

Table 3: Feature History for Router Recovery with the ROM Monitor

ModificationRelease

A new board, RSP3 was introduced.Release 4.2.0

• Information About Router Recovery, page 21

• About ROMMON Installation Files, page 22

• About the TURBOBOOT Variable, page 25

• About the Boot Device (Destination Disk), page 26

• Reinstalling Cisco IOS XR Software on Cisco ASR 9000 Series Router, page 27


Information About Router RecoveryThe standard way to install new software on the RSP card of a Cisco ASR 9000 Series Aggregation ServicesRouter is by using the install command in administration EXEC mode. However, if the RSP card is unableto boot the Cisco IOS XR software or you want to completely replace the existing software, you can reinstallthe software while the RSP card is in ROMMonitor mode. When you install the Cisco IOS XR software fromROMMonitor mode, you must use a special software installation file with a vm file extension. These filesare called vm files. You cannot install software in package installation envelope (PIE) files from ROMMonitormode.

Installation using a vm file in ROM Monitor mode should be performed only from the RSP card of thesystem.

Note


Reinstalling the Cisco IOS XR software from ROMMonitor mode replaces the currently installed routersoftware and causes substantial router downtime.We recommend installing or upgrading software packagesfrom administration EXECmode using PIE files, as described in theUpgrading and Managing Cisco IOSXR Software module of the Cisco ASR 9000 Series Aggregation Services Router System ManagementConfiguration Guide.

Caution

About ROMMON Installation FilesThis section includes the following topics:

Locating Installable FilesTo obtain Cisco IOS XR software and version information, use the Cisco Software Delivery System (SDS),available at the following URL:

http://www.cisco.com/cisco/software/navigator.html?mdfid=279844343&flowid=2130

To locate Cisco IOS XR software images:

• Select any entry under Cisco ASR 9000 Series Aggregation Services Routers.

• Select IOS XR software to see the image tar files, or choose any of the other categories to see the otherfiles.

The table below lists the software packages that you can install from ROMMON.

Table 4: Downloadable Software for Installation from ROM Monitor

DescriptionSoftware Package Name

This package contains two copies of the Cisco IOSXRUnicast Routing CoreBundle. One copy is in the Package Installation Envelope (PIE) file formatand can be installed while Cisco IOS XR is running, as described intheUpgrading and Managing Cisco IOS XR Software module of theCisco ASR 9000 Series Aggregation Services Router System ManagementConfiguration Guide. The other copy is in a vm file that can be installedfrom ROMMonitor. This package also includes Cisco IOS XR MPLS,Manageability, and Multicast packages (in PIE files).

Cisco IOSXR IP/MPLSCoreSoftware

This package contains everything in the Cisco IOS XR IP/MPLS CoreSoftware package in addition to Cisco IOS XR Security package (in a PIEfile).

Cisco IOSXR IP/MPLSCoreSoftware 3DES

The table above lists packages that are distributed in files with tar filename extensions (tar files are assembledwith the UNIX tar utility).When you download a tar file, you must unpack the tar file with a software programbefore you can install any of the files in the package.


Router Recovery with ROM MonitorAbout ROMMON Installation Files

http://www.cisco.com/cisco/software/navigator.html?mdfid=279844343&flowid=2130

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

The tar files contain both PIE files and vm files. If the router is operating properly, you can install thesoftware using the appropriate PIE file with little or no interruption to router traffic, as described in theUpgrading and Managing Cisco IOS XR Software module of the Cisco ASR 9000 Series AggregationServices Router System Management Configuration Guide. If the router is not booted with theCisco IOS XR software, install the core software using the vm file first, and then install any additionalpackages using the PIE files after the router enters EXEC mode.

Note

tar Filenames and Version NumbersThe format for a tar filename is:

platform-bundle_name-major.minor.maintenance.tar

Table 5: tar Filename Components

DescriptionComponent

Identifies the platform for which the software package is designed.

For packages designed for the Cisco ASR 9000 Series Aggregation Services Routers,the platform designation is "ASR9k."

platform

Identifies a specific bundle.

• IOS XR bundle name indicates a file that includes all packages in the CiscoIOSXRUnicast Routing Core Bundle and theManagement,MPLS, andMulticastpackages. These packages are described in the Upgrading and Managing CiscoIOS XR Softwaremodule of Cisco ASR 9000 Series Aggregation Services RouterSystem Management Configuration Guide.

• IOS XR-k9 bundle name indicates a file that includes all packages in the iosxrbundle file plus the security package.

bundle_name

Identifies the major release of this package.

• Major releases occur 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.

• Major release is the least frequent release and may require a router reboot.

major


Router Recovery with ROM Monitortar Filenames and Version Numbers


Identifies the minor release of this package.

• Minor releases contain one or more of the following:

◦New features

◦Bug fixes

• Minor release versions do not have to be identical for all software packagesoperating on the router, but the operating packages must be certified by Ciscoas compatible with each other.

• Minor releases may require a router reboot.

minor

Identifies the maintenance release of this package.

• Maintenance releases contain a collection of bug fixes for a package.

• Maintenance release versions do not have to be identical for all software packagesoperating on the router, but the major and minor versions of the maintenancerelease must match the those of the package being updated.

• Maintenance releases usually do not require a router reboot.

maintenance

vm Filenames and Version NumbersThe format for a vm filename for Cisco ASR 9000 Series Aggregation Services Routers is:

platform-package_name.vm-major.minor.maintenance

The table below describes the other filename components.

Table 6: vm Filename Components


Identifies the platform for which the software package is designed.

For packages designed for Cisco ASR 9000 Series Aggregation Services Routers, theplatform designation is “asr9k”.

platform

Identifies a specific package.

• Mini package names indicate a composite package that includes all packages inthe Cisco IOS XR Unicast Routing Core Bundle, which is described in theUpgrading and Managing Cisco IOS XR Software module of Cisco ASR 9000Series Aggregation Services Router System Management Configuration Guide.

package_name


Router Recovery with ROM Monitorvm Filenames and Version Numbers


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.

major

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 packagesoperating on the router, but the operating packages must be certified by Cisco ascompatible with each other.

• A minor release may require a router reboot.

minor

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 softwarepackages operating on the router, but the major and minor versions of themaintenance release must match the those of the package being updated.

• A maintenance release usually does not require a router reboot.

maintenance

The following example shows a composite of multiple mini packages:

comp-asr9k-mini.vm-5.2.0

About the TURBOBOOT VariableThe TURBOBOOT environmental variable automates the software installation process in the ROMMonitormode and determines the installation settings, such as the boot device (destination disk) for software installation.

Running TURBOBOOT from harddisk: with the TURBOBOOT file located on harddisk: is not supported.Save the TURBOBOOT file on TFTP server or on USB drive to successfully install the package.

Note

The following is the syntax for the TURBOBOOT environmental variable:

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


Router Recovery with ROM MonitorAbout the TURBOBOOT Variable

In the preceding example, the TURBOBOOT variable is set to on, the boot device (destination disk) is theflash disk in disk0:, the installation process formats the disk, and the installation process can be terminatedprematurely.

TURBOBOOT=on,disk0,format,nodisablebreakThere are four main arguments and keywords for the TURBOBOOT variable:

• on—Installs and activates the Cisco IOS XR software packages when the RSP is booted with the vmimage.

• boot-device—Selects the destination disk for software installation.

• [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 . When the format option isselected, the Cisco IOS XR software is completely replaced, and only the administration configurationis preserved. All other files on the disk, including all configuration files and all user files, are deleted.The administration configuration contains the configuration that determines default- SDR name andinventory.

• [nodisablebreak]: When the nodisablebreak flag is added, the installation process using theTURBOBOOT variable can be prematurely terminated by sending a break from the terminal. The defaultis to ignore breaks from the terminal.

Note • Each argument is separated by a comma.

• The default boot device disk is disk0:.

About the Boot Device (Destination Disk)The boot device determines the location where the Cisco IOS XR software is installed on all RSPs. The systemuses the boot-device to install the software to the other RSP card in the system. Any additional software orsoftware upgrades are automatically saved to the same boot device.

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

The Cisco IOS XR package is installed on the boot device (disk0: or disk1:) and the minimal boot image(MBI) is installed on the bootflash: device. The MBI contains the low level Cisco IOS XR drivers andsubsequently makes the full Cisco IOS XR software environment available on the router. The ROMMonitorsoftware loads the MBI from the bootflash: device.

• MBI is always installed on the boot device.

• On the Cisco ASR 9000 Series Router, the supported boot devices are disk0: and disk1:.

On the RSP3 card, the Cisco IOS XR software is installed directly on either disk0 or disk1.Note


Router Recovery with ROM MonitorAbout the Boot Device (Destination Disk)

After the Cisco IOSXR software is installed to the boot device using the TURBOBOOTmethod, all additionalsoftware and software upgrades are automatically installed and synchronized to that same boot device andcannot be changed. For example:

• If the Cisco IOS XR software is installed in the RSP card using the TURBOBOOT variable, with disk0(TURBOBOOT=on,disk0), all packages are installed to disk0: and the boot device is disk0:.

• If the Cisco IOS XR software is installed in the RSP card using the TURBOBOOT variable, with disk1(TURBOBOOT=on,disk1), all packages are installed to disk1: and the boot device is “disk1:”.

• After you boot the Cisco IOS XR software, you are not allowed to add packages to anywhere other thanthe boot-device. For example, you cannot boot the DSC to disk1: and decide to add your packages todisk0: or vice versa.

We recommend using disk0: as the boot device. Disk0: is pre-installed in most RSPs, which ensures thatthe correct disk is used to store the software packages on the entire system.

Note

Reinstalling Cisco IOS XR Software on Cisco ASR 9000 SeriesRouter

Reinstalling Cisco IOS XR software from ROMMonitor mode replaces the currently installed routersoftware and causes substantial router downtime. We recommend that you install or upgrade softwarepackages from the Administration EXECmode using package installation envelope (PIE) files, as describedin the Upgrading and Managing Cisco IOS XR Software module of Cisco ASR 9000 Series AggregationServices Router System Management Configuration Guide.

Caution

This section includes the following topics:

Cisco ASR 9000 Series Router Router Installation OverviewWhen you reinstall the software fromROMMonitor mode, you can perform either of the following procedures:

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

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

Installation from a TFTP ServerWhen you install Cisco IOS XR software from a TFTP server to the RSP, you must perform the followingtasks:

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

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


Router Recovery with ROM MonitorReinstalling Cisco IOS XR Software on Cisco ASR 9000 Series Router

3 Place all RSPs in ROM Monitor mode.

4 From the ROM Monitor mode, clear BOOT and TFTP_FILE ROMMonitor environmental variables onall RSP cards. If disk mirroring is enabled, disable disk mirroring by clearing BOOT_DEV_SEQ_OPERand MIRROR_ENABLE ROMMonitor environment variables.

Restore disk mirroring after the Cisco IOS XR installation is complete using the TURBOBOOT variable.To restore disk mirroring, use themirror command in the global configurationmode. For more informationon themirror command, see the “Boot Commands on Cisco IOS XR Software” module inCisco ASR 9000 Series Aggregation Services Router System Management Command Reference.

Note

5 Use the confreg command in the ROM Monitor mode to set all the RSP cards to MBI Validation BootMode or the EXEC mode.

6 On the active RSP, configure the IP parameters (IP_ADDRESS, DEFAULT_GATEWAY,IP_SUBNET_MASK) for the Management Ethernet interface. These variables are set in ROMMonitor,and are required to access the TFTP server.

7 On the active RSP, configure the TURBOBOOT environment variable to either clean or format the bootdisk during the installation. The recommended boot device is disk0:.

8 On the active RSP, boot the Cisco IOS XR software from a vm file on the TFTP server.

9 Reset all other RSPs to boot the Cisco IOS XR software.

After you boot the Cisco IOS XR software, the TURBOBOOT process either cleans or formats the bootdevice, based on the TURBOBOOT environment variable setting.

Note

10 Restore disk mirroring if it was disabled in "Step 4". To restore disk mirroring, use themirror commandin the global configuration mode. For more information on themirror command, see the Boot Commandson Cisco IOS XR Software module in Cisco ASR 9000 Series Aggregation Services Router SystemManagement Command Reference.

If the TURBOBOOT variable is set to format the boot device, the default-SDR configuration is deletedand only the admin configuration is preserved.

Caution

Reinstalling to a CiscoASR 9000 SeriesRouter from a TFTP Server ImageCisco IOS XR software can be reinstalled directly from a vm file located on a TFTP server. Complete theinstructions in this section exactly as described.


Router Recovery with ROM MonitorReinstalling to a CiscoASR 9000 SeriesRouter from a TFTP Server Image

Reinstalling to a Cisco ASR 9000 Series Router from a TFTP Server Image

Before You Begin

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

• ROMMonitor firmware on the Cisco ASR 9000 Series Router is compatible with the Cisco IOS XRsoftware image that you are installing.

• The following information is available:

◦IP address of the Management Ethernet interface on the RSP

◦Subnet mask of the Management Ethernet interface on the RSP

◦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

◦Boot device for your system.

On the RSP3 card, the ROMMON variable TFTP_MGMT_INTF=port_no is not required for a TFTPboot.

Note



SUMMARY STEPS

1. Back up the router configuration while still in EXEC mode.2. Verify the sanity of the configuration file system. Use cfs check3. admin4. Place all RSP cards in ROM Monitor mode. Use config-register boot-mode rom-monitor location all

and reload location all commands.5. Clear the ROM Monitor environmental variables on all RSP cards. Use unset BOOT command, unset

TFTP_FILE command and sync command.6. Clear the ROM Monitor environment variables BOOT_DEV_SEQ_OPER and MIRROR_ENABLE, if

disk mirroring is enabled. Use unset BOOT_DEV_SEQ_OPER command, unsetMIRROR_ENABLEcommand and sync command.

7. On the RSP card , set the environment variables that configure the Management Ethernet interface for usein ROMMonitormode. Use IP_ADDRESS=ip_address command, IP_SUBNET_MASK=mask commandand DEFAULT_GATEWAY=ip_address command.

8. On the RSP card , set the TFTP environment variables. Use TFTP_VERBOSE=print_setting command,TFTP_RETRY_COUNT=retry_count command, TFTP_TIMEOUT=timeout command,TFTP_CHECKSUM=0 command, TFTP_SERVER=server_ip_addr command,TFTP_MGMT_INTF=port_no command

9. On the RSP card , set the TURBOBOOT variables. UseTURBOBOOT=on,boot-device,options commandand sync command.

10. On the RSP card , boot the vm image located on the tftp server. Use boot tftp://server/directory/filename11. Reset all other RSP cards to boot the Cisco IOS XR software. Use confreg and reset commands.12. Restore disk mirroring, if it was disabled in “Step 5”.

DETAILED STEPS


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

Back up the router configuration while still in EXECmode.Step 1

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

Verify the sanity of the configuration file system. Use cfscheck

Step 2

Example:

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

Note • This step is necessary only to preserve the routerconfigurations (if TURBOBOOT variable is setto clean). If TURBOBOOT variable is set toformat, then the disk is erased and the existingconfigurations are deleted. The default option isclean.

Enters the admin EXEC mode.admin

Example:

RP/0/RSP0/CPU0:router# admin

Step 3




Place all RSP cards in ROM Monitor mode. Useconfig-register boot-mode rom-monitor location all andreload location all commands.

Step 4

Example:

RP/0/RSP0/CPU0:router(admin)# config-registerboot-mode rom-monitor location allRP/0/RSP0/CPU0:router(admin)# reload location all

Ensures that all RSP cards in the system are prepared forinstallation using the TURBOBOOT variable. Repeat for eachRSP card in the system (LCC).

Clear the ROM Monitor environmental variables on allRSP cards. Use unset BOOT command, unsetTFTP_FILE command and sync command.

Step 5

Example:

rommon B1> unset BOOT

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

All variable names are case sensitive.rommon B2> unset TFTP_FILErommon B3> sync • Clears the BOOT variable.

• Clears the TFTP_FILE variable.

• Saves the changes.Note • If the unset command displays an error

message, it is most likely because thevariable you are trying to change is not set.If this is the case, ignore the message andcontinue.

If disk mirroring is enabled, clear theBOOT_DEV_SEQ_OPER andMIRROR_ENABLE ROMMonitor environment variables to disable disk mirroring.

Clear the ROM Monitor environment variablesBOOT_DEV_SEQ_OPER and MIRROR_ENABLE, ifdisk mirroring is enabled. Use unset

Step 6

BOOT_DEV_SEQ_OPER command, unsetMIRROR_ENABLE command and sync command.

All variable names are case sensitive.

• Clears the BOOT_DEV_SEQ_OPER variable.Example: • Clears the MIRROR_ENABLE variable.Example

rommon B1> unset BOOT_DEV_SEQ_OPER

• Saves the changes.Note • Restore the disk mirroring settings once the

installation is complete using theTURBOBOOT variable. Disk mirroring isrestored in the global configuration modeusing themirror command.

rommon B2> unset MIRROR_ENABLErommon B3> sync

Enter these settings exactly as shown. All variable names arecase sensitive.

On the RSP card , set the environment variables thatconfigure the Management Ethernet interface for use in

Step 7

ROMMonitor mode. Use IP_ADDRESS=ip_address




• Sets the IP address for the Management Ethernet interfaceon the RSP card .

command, IP_SUBNET_MASK=mask command andDEFAULT_GATEWAY=ip_address command.

Example:

rommon B4> IP_ADDRESS=1.1.1.1

• Sets the subnet mask for the Management Ethernetinterface on the RSP card .

• Identifies the default gateway that serves the RSP card .rommon B5> IP_SUBNET_MASK=255.255.254.0rommon B6> DEFAULT_GATEWAY=1.1.0.1

(Optional) Enter these settings exactly as shown. All variablenames are case sensitive.

On the RSP card , set the TFTP environment variables. UseTFTP_VERBOSE=print_setting command,

Step 8

TFTP_RETRY_COUNT=retry_count command,• TFTP_VERBOSE sets the printer setting: 0=quiet,1=progress (default), 2=verbose.

TFTP_TIMEOUT=timeout command,TFTP_CHECKSUM=0 command,TFTP_SERVER=server_ip_addr command,TFTP_MGMT_INTF=port_no command

• TFTP_RETRY_COUNT sets the retry count for ARPand TFTP (default=18).

Example:• TFTP_TIMEOUT sets the overall timeout of the operationin seconds (default=7200).Example

rommon B4> TFTP_VERBOSE=0• TFTP_CHECKSUM specifies whether or not to performa checksum test on the image: 0=no, 1=yes.

rommon B5> TFTP_RETRY_COUNT=4rommon B6> TFTP_TIMEOUT=6000 • TFTP_SERVER sets the IP address of the TFTP server

where a bootable software image is located.rommon B7> TFTP_CHECKSUM=0rommon B8> TFTP_SERVER=223.255.255.254rommon B9> TFTP_MGMT_INTF=0

• TFTP_MGMT_INTF determines the RSP cardManagement LAN port to use for TFTP. The default valueis port 0.

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

On the RSP card , set the TURBOBOOT variables. UseTURBOBOOT=on,boot-device,options command andsync command.

Step 9

Example:

rommon B9> TURBOBOOT=on,disk0,formatrommon B10> sync

• To enable the installation process using the TURBOBOOTvariable, specify on.

• Specify a boot device where all software is installed onthe RSP cards. We recommend disk0.

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

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

• Default option is clean.

• Any existing configuration is preserved.

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

On the RSP card , boot the vm image located on the tftpserver. Use boot tftp://server/directory/filename

Step 10




Example:

rommon B11> boot

• Run this command on the RSP card and specify the vminstallation file from the TFTP server.

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

tftp://223.255.254.254/softdir/comp-asr9k-mini.vm

• Allow the system to fully boot. The installation processusing the TURBOBOOT variable takes some time. Do notenter any commands until you are prompted to enter ausername or until the CLI prompt appears.

• “Press RETURN to get started” appears twice. The firstoccurrence appears when the software is loaded intomemory. The second occurrence happens after the softwarehas been installed on the disk.

• RSP card is fully booted when the following messageappears:

SYSTEM CONFIGURATION COMPLETED

Reset all other RSP cards to boot theCisco IOSXR software. Use confreg and reset commands.

Step 11 • The confreg command displays a series of prompts tochange the configuration register. To reset to EXECmode,select the boot type as 2 when prompted.

Example:

rommon B4> confregrommon B5> reset

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

• Resets the RSP card and starts the boot process.

To restore disk mirroring, use themirror command in the globalconfiguration mode.

Restore disk mirroring, if it was disabled in “Step 5”.

Example:rommon B6 mirror

Step 12

Reinstalling to a Cisco ASR 9000 Series Router from a TFTP Server Image: Example

The following example shows how to install the Cisco IOS XR software from the TFTP server:

Place all RSPs in ROM Monitor mode:

RP/0/RSP0/CPU0:router# adminRP/0/RSP0/CPU0:router(admin)# config-register boot-mode rom-monitorRP/0/RSP0/CPU0:router(admin)# location allRP/0/RSP0/CPU0:router(admin)# reload location allClear the ROM Monitor environmental variables on all RSPs:

rommon B1 > unset BOOT



rommon B2 > unset TFTP_FILErommon B3 > syncClear the ROM Monitor environment variables for disk mirroring:

rommon B1 > unset BOOT_DEV_SEQ_OPERrommon B2 > unset MIRROR_ENABLErommon B3 > sync

Restore disk mirroring settings after the installation is complete using the TURBOBOOT variable. Diskmirroring is restored using themirror command in the global configuration mode. For more informationon themirror command, see the “Boot Commands on Cisco IOS XR Software” module inCisco ASR 9000 Series Aggregation Services Router System Management Command Reference.

Note

Set the IP environment variables to configure the ROMMonitor Management Ethernet interface on the RSP:

rommon B4 > IP_ADDRESS=10.1.1.1rommon B5 > IP_SUBNET_MASK=255.255.254.0rommon B6 > DEFAULT_GATEWAY=10.1.0.1Enable installation process using the TURBOBOOT variable on the RSP. The following example shows howto boot the router using the specified vm file on the specified TFTP server:

rommon B7 > TURBOBOOT=on,disk0,formatrommon B8 > syncrommon B9 > boot tftp://10.10.10.10/software/comp-asr9k-mini.vmReset all other RSPs to boot the Cisco IOS XR software:

Respond to the prompts as instructed. Set the boot type as 2 to boot the RSP card in EXEC mode:

rommon B11 > reset

Installing Cisco IOS XR Software on Cisco ASR 9000 Series Router from a USBDrive

Before You Begin

Verify that the following prerequisites are met:

• Cisco IOS XR 5.2.0-px file is available in the USB drive.

• RSP 440 is installed.

• Console access to active RSP 440 is available.


Router Recovery with ROM MonitorInstalling Cisco IOS XR Software on Cisco ASR 9000 Series Router from a USB Drive

SUMMARY STEPS

1. Verify that the router is in a steady state.2. Connect a terminal to the RSP card console port and log in to the router.3. Place all the PSP cards in ROMMonitor mode. Use the config-register boot-mode rom-monitor location

all command.4. Insert the USB into the slot on the RSP. Use the reload location all command.5. Use dir usb6. Clear the ROMMonitor environmental variables on all RSP cards. Use unset BOOT and sync commands.7. Set the TURBOBOOT variables on the RSP card. Use TURBOBOOT=on ,disk 0,format and sync

commands.8. Install Cisco IOS XR 5.2.0-px from the USB. Usemediaboot usb:\ filename

DETAILED STEPS


Ensures that all configurations are saved and that no installationprocesses are running.

Verify that the router is in a steady state.Step 1

Connects a terminal or PC to the RSP card console port andestablishes a router management session.

Connect a terminal to the RSP card console portand log in to the router.

Example:rommon B1>

Step 2

Place all the PSP cards in ROMMonitor mode. Usethe

Step 3

config-register boot-mode rom-monitor locationall command.

Example:

RP/0/RSP0/CPU0:router(admin)#config-register boot-mode rom-monitorlocation all

Reboots into the ROMMON mode and detects the newly insertedUSB drive.

Insert the USB into the slot on the RSP. Use thereload location all command.

Step 4

Example:

RP/0/RSP0/CPU0:router(admin)# reloadlocation all

After the RSP reboots into ROMMON, use the devcommand to list the devices connected to the RSP. Ensurethat the device of type compactflash is mounted.

Note

Displays the contents of the USB drive.Use dir usb

Example:

rommon B1> dir usb

Step 5


Router Recovery with ROM MonitorInstalling Cisco IOS XR Software on Cisco ASR 9000 Series Router from a USB Drive


Ensures that all RSP cards in the system are prepared for installationusing the TURBOBOOT variable. Repeat for each RSP card in the

Clear the ROM Monitor environmental variableson all RSP cards. Use unset BOOT and synccommands.

Step 6

system (LCC). Enter the settings exactly as shown. You must attacha terminal to each card for this procedure.

Example:

rommon B2> unset BOOTrommon B3> sync

All variable names are case sensitive.

• Clears the BOOT variable.

• Saves the changes.

If the unset command displays an error message, it is mostlikely because the variable you are trying to change is notset. If this is the case, ignore the message and continue.

Note

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

Set the TURBOBOOT variables on the RSP card.Use TURBOBOOT=on ,disk 0,format and synccommands.

Step 7

• To enable the installation process using the TURBOBOOTvariable, specify on.

Example:

rommon B4> TURBOBOOT=on,disk0,formatrommon B5> sync

• Specify a boot device where all software is installed on theRSP cards. We recommend disk0.

• The default option is clean. To replace the existing softwarewithout formatting the boot device, replace options with clean.

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

Starts the boot process for the Cisco IOSXR Software on Cisco ASR9000 Series Router. With the turboboot option set, all the files areinstalled on disk0.

Install Cisco IOS XR 5.2.0-px from the USB. Usemediaboot usb:\ filename

Example:

rommon B6> mediaboot usb:\

Step 8

asr9k-mini-px.vm-5.2.0

What to Do NextAfter the system is up and in EXEC mode, you can execute the full range of CLI commands from the RSPcard.

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

Note


Router Recovery with ROM MonitorWhat to Do Next

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

• For instructions on how to verify that the interfaces are up and properly configured, see Verifying theSystem Interfaces in the

• Install additional software from the PIE files, as necessary. For more information, see the Upgradingand Managing Cisco IOS XR Software module of Cisco ASR 9000 Series Aggregation Services RouterSystem Management Configuration Guide.

Additional ReferencesThe following sections provide references related to the ROM Monitor.

Related DocumentsDocument TitleRelated Topic

“Obtaining Additional Publications and Information” inWhat’s New in Cisco Product Documentation located at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Contact a Cisco representative

Upgrading and Managing Cisco IOS XR Softwaremodule ofCisco ASR 9000 Series Aggregation Services Router GettingStarted Guide

Save current router configuration

Verify that interfaces are up and properlyconfigured

Install or upgrade software packages fromPIE files

Managing the Router Hardware module ofCisco ASR 9000 Series Aggregation Services Router GettingStarted Guide

Redundancy slot pairs


Router Recovery with ROM MonitorAdditional References

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Technical AssistanceLinkDescription

http://www.cisco.com/supportThe Cisco Support website provides extensiveonline resources, including documentation andtools for troubleshooting and resolving technicalissues with Cisco products and technologies.

To receive security and technical informationabout your products, you can subscribe tovarious services, such as the Product Alert Tool(accessed from Field Notices), the CiscoTechnical Services Newsletter, and ReallySimple Syndication (RSS) Feeds.

Access to most tools on the Cisco Supportwebsite requires a Cisco.com user ID andpassword.


Router Recovery with ROM MonitorTechnical Assistance

http://www.cisco.com/support

C H A P T E R 4Managing Configuration Files in ROM Monitor

This chapter provides information about managing configuration files in the router.

• Information about Configuration Files, page 39

• Specifying an Alternative Administration Configuration, page 40

• Specifying an Alternative SDR Configuration, page 46

• Specifying an Alternate Storage Location for Configuration Files, page 53


Information about Configuration FilesCisco IOS XR software creates two types of configuration files—the administration configuration file andthe default secure domain router (SDR) configuration files. These configuration files are stored in the followinglocations:

• There is only one administration configuration file, which is stored on the RSP and contains system-wideconfigurations for items such as SDR name and node inventory.

• There is only one SDR configuration file in Cisco ASR 9000 Series Router, which is stored on the RSPto specify the parameters for routing, interfaces, SDR usernames, and other SDR-specific configurations.

The Cisco ASR 9000 Series Router contains only one SDR (the default SDR). In Cisco IOS-XR software,SDRs are a means of dividing a single physical system into multiple logically separated routers.Cisco ASR 9000 Series Aggregation Services Routers are single-shelf routers that support only one SDR pershelf.

For more information on SDRs and admin plane configuration, see the Configuring Secure Domain Routerson Cisco IOS XR Software module of the Cisco ASR 9000 Series Aggregation Services Router SystemManagement Configuration Guide.

The following sections describe ways to manage the use of configuration files from ROMMonitor:


The default configuration should be sufficient for most situations. The options described in the followingsections are for rare cases in which an alternative configuration is required. Use of these options can resultin system errors or downtime. Consult Cisco technical support before using these options.

Caution

Specifying an Alternative Administration ConfigurationThe administration configuration stores system-wide configurations such as the SDR name and node inventoryfor the entire system. This is separate from the default-SDR configuration that stores routing and interfaceconfigurations.

The default committed administration configuration should be sufficient for most situations. The optiondescribed in this section is for rare cases when an alternative admin configuration is required. Use of thismethod can result in system errors or downtime.

Caution

Specifying a Temporary Alternative Administrative Configuration with the -oBoot Option

This mode of administrative configuration with the -o boot option is temporary in nature. After this bootoption is set, this mode allows the router to boot from this alternative configuration, and the configurationspecified in this configuration file becomes part of the running and persistent configuration.

When the router boots with the external configuration specified by the -o option, the system loses thedefault configuration. The default configuration is completely replaced with this alternative configuration.

Note

To specify a temporary administration configuration file with the -o boot option, use the following procedure.With this method, the specified configuration file is used for a single router boot. If the RSP is reset again,the permanent configuration file is used.


Managing Configuration Files in ROM MonitorSpecifying an Alternative Administration Configuration

SUMMARY STEPS

1. Place the RSP and the standby RSP in ROM Monitor mode.2. confreg3. Enter boot type as 0.4. reset5. confreg6. Enter boot type as 2.7. set8. boot image –o config-file-path9. confreg10. Enter boot type as 2.11. reset

DETAILED STEPS


Place the RSP and the standby RSP in ROM Monitormode.

Step 1

Sets the configuration register of the standby RSP to ROMMonitor mode so that the standby RSP does not take control.

confreg

Example:

rommon B1 > confreg

Step 2

Enter the confreg command at the ROMMonitormode promptto set the configuration register to ROM Monitor mode. Youcan also change the console baud rate, boot characteristics,boot type configuration settings, and enable diagnostic modeat the ROM Monitor mode.

Configuration Summary(Virtual Configuration Register: 0x1920)enabled are:

The configuration register is not an environmentvariable like TURBOBOOT. Do not enter an equalsign when entering the confreg command.

Noteconsole baud: 9600boot: the ROM Monitordo you wish to change the configuration? y/n [n]:yenable "diagnostic mode"? y/n [n]: nchange console baud rate? y/n [n]: nchange the boot characteristics? y/n [n]: yenter boot type:0 = ROM Monitor2 = MBI Validation Boot Mode[0]: 0

Sets the boot type as 0 to enable ROMMonitor mode duringthe next system

ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2 · ROM...

Documents

Transcript of ROM Monitor Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 5.2 · ROM...