Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.8
Migrating from Cisco IOS to Cisco IOS XR Software
Downloads: This chapterpdf (PDF - 0.98MB) The complete bookPDF (PDF - 2.37MB) | Feedback

Migrating from Cisco IOS to Cisco IOS XR Software

Table Of Contents

Migrating from Cisco IOS to Cisco IOS XR Software

Contents

Prerequisites for Migration

Restrictions for Migration

Information About Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router

Network Audits

Pre-migration Audit

Post-migration Audit

Hardware Audit

Software Audit

Firmware Audit

Audit Checklist

Migration Methodology Considerations

Direct Migration

Pre-staged Migration

Comparison of Direct and Pre-staged Migration Stategies

Scheduling the Operating System Cutover

How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software

Verifying Your Cisco IOS Image

Verifying Cisco IOS Boothelper

Verifying Cisco ROM Monitor

Verifying Line Card Firmware

Verifying Line Card Physical Memory

How to Perform a Direct Migration

Prerequisites for Direct Migration

Restrictions for Direct Migration

Preparing the Target Device

Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router

How to Perform a Pre-staged Migration

Prerequisites for Pre-staged Migrations

Restrictions for Pre-staged Migrations

Swapping Disks

Creating a Disk Backup with a Golden Disk

Mirroring a Disk

Cloning a Disk

Swapping a PRP

What to Do If Your Migration Fails

Troubleshooting a Failed Migration

Reverting to Cisco IOS from Cisco IOS XR Software

Migrating from Cisco IOS to Cisco IOS XR Software: Examples

How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software: Examples

Verifying Your Cisco IOS Image: Example

Verifying Cisco IOS Boothelper: Example

Verifying Cisco ROM Monitor: Example

Verifying Cisco IOS Firmware: Example

Verifying Line Card Memory: Example

How to Perform a Direct Migration: Example

Installing Cisco IOS XR Software on the Primary RP: Example

Installing Cisco IOS XR Software on a Standby RP: Example

How to Perform a Pre-staged Migration: Example

Troubleshooting a Failed Migration: Examples

Upgrading the Mbus Firmware: Example

Verifying the Field-Programmable Devices in All Slots: Example

Upgrading the Fabric Downloader: Example

Reverting to Cisco IOS from Cisco IOS XR Software: Example

Additional References

Related Documents

Technical Assistance


Migrating from Cisco IOS to Cisco IOS XR Software


This document describes the process for migration from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router. Although the information provided applies particularly to Cisco IOS XR Software Release 3.8.0, much of the guidance offered is valuable independent of any given release.


Note The term Cisco XR 12000 Series Router is used in this document tomean either an original chassis (such as the GSR10/200-DC) or an enhanced chassis (for example, the Cisco 12000/10) that is ready for Cisco IOS XR software.


Feature History for Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router

Release
Modification

Release 3.2

Support for Cisco IOS XR software was introduced on the Cisco XR 12000 Series Router.

This document was introduced as Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

Title of this publication was changed from Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router to Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.

Document was completely rewritten.

Release 3.6.0

Documentation content was reorganized to be more in compliance with Cisco IOS Structured Authoring Writing Guidelines.

Release 3.7.0

No modification.

Release 3.8.0

Support was added for the 4-GB flash disk and PRP3.

New information about pre-staged migration methods was added and other content was reorganized and rewritten.


Contents

Prerequisites for Migration

Restrictions for Migration

Information About Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router

How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software

How to Perform a Direct Migration

How to Perform a Pre-staged Migration

What to Do If Your Migration Fails

Migrating from Cisco IOS to Cisco IOS XR Software: Examples

Additional References

Prerequisites for Migration

Before you can migrate from Cisco IOS to Cisco IOS XR software, you must performed the following tasks:

You should have already identified the Cisco IOS XR software release to which you want to migrate.

We recommend that you base this decision on the Cisco IOS software features you currently use and on which Cisco IOS XR software features you hope to use in future.


Note We strongly suggest that you consult with Cisco Technical Support staff before making a decision about which Cisco IOS XR release to install.


You should have reviewed Restrictions for Migration.

You should have completed a network audit during which you compared the hardware, software, line card memory, and firmware requirements stated in the Cisco IOS XR Release Notes for the release you want to install, against what is currently on all the nodes of your Cisco IOS network. The minimum requirements for the release, which should be used as part of your network audit, are described in Table 2 and in the Cisco IOS XR Release Notes.

You should have acquired a valid Cisco IOS software image for your router. Make sure that the image supports your hardware and software features and that your router has enough memory to run it. See Table 2 for details.

You should have identified the Cisco IOS configurations you wanted to keep and should have scheduled time to reconfigure these following migration, or to contact Cisco Technical Support to expedite the process.

You should have reviewed the pros and cons of the various migration methods. See Migration Methodology Considerations.

You should have determined a cutover schedule, as described in Scheduling the Operating System Cutover.

Restrictions for Migration

The migration process includes the following important restrictions for installing Cisco IOS XR software:

Important syntax differences exist between Cisco IOS and Cisco IOS XR software. As a result, Cisco IOS configurations do not migrate cleanly:

You will need to reconfigure these configurations from scratch in Cisco IOS XR software. Therefore, consider carefully which Cisco IOS software configurations you really want to use after the migration. You may not need all of them in the new operating system, which will save you work later.

If you have many nodes with configurations you must keep, so that creating them from scratch is not an option, consider contacting Cisco Technical Support, who can expedite this.

All media must always be installed to the same slot on each route processor or the migration will fail.

Information About Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router

Network Audits

Migration Methodology Considerations

Network Audits

There are two types of audits in a migration from Cisco IOS to Cisco IOS XR software:

Pre-migration Audit

Post-migration Audit

Pre-migration Audit


Caution These requirements are not flexible. If the minimum levels are not met, problems will be encountered during the migration.

A pre-migration network audit guarantees that all network components on which the target release has dependencies are current. The audit must be performed before migration can take place. Otherwise, the migration will with likelihood not succeed and you will have lost valuable time and have created an avoidable and lengthy disruption to service.

Depending on the results from the audit, the upgrade itself may take up to 40 minutes (or more). The length of time depends on how many elements in your system require an upgrade.

Post-migration Audit

After you have cutover to the Cisco IOS XR operating system, you will also want to perform a post-migration audit. This audit should concentrate on ensuring that the router:

Has all of the appropriate levels of firmware

Has all of the expected packages of software installed and activated

Is operating correctly and efficiently

Hardware Audit

This section describes the role played by the audited hardware components and why it is important that each meets the specified requirements. (For release-specific requirements, see also http://wwwin.cisco.com/sptg/crbu/products/12000/xr12000/migration.shtml.)

Route Processor

The route processor is responsible for the following functions:

Booting the router/software

Handling FIB updates to line cards

Routing protocol operation

Routing policy application

Management

Supported Route Processors

Cisco supports the deployment of Cisco IOS XR software on the following route processors (RPs) installed in a Cisco XR 12000 Series Router:

PRP2

PRP3


Note PRP3 is available only for Cisco IOS XR Software Release 3.8.0 and later releases.


High Availability

Under standard conditions, each Cisco XR 12000 Series Router chassis operates with two route processors to provide redundancy in the event of a route processor (RP) failure. The dual RPs operate in active/standby mode to be ready for a switchover in case the primary RP fails.

For dual RPs to interoperate within the same chassis, each RP within that chassis must be identical in terms of Cisco IOS XR software revision, route memory, and storage media.


Note We do not recommend the use of a single RP within a Cisco XR 12000 Series Router chassis.


PRP-2 Storage Requirements

The PRP-2 has two locations that can be used for media storage:

On-board compact flash disk

External PCMCIA slots—Recommended for the primary boot location, with each slot populated with a 2-GB-minimum flash disk.

Each location has advantages and disadvantages for storing the RP functions (log files, route configuration, software packages, backup software images).

On-Board Compact Flash Disk Advantages

The advantage of the on-board compact flash disk is that it is not accessible from the front panel of the route processor, whereas, the external PCMCIA slots are. Because of this easy access to the external PCMCIA slots, the flash card could be easily removed, unintentionally bringing down the system.

Also, to be able to remove the flash card, you must remove the route processor itself, which would never be done casually.

Another advantage to the use of the on-board compact flash disk as a primary boot device, as compared to an external flash disk, is that the on-board compact flash disk is easier to upgrade. Its external location allows you to unmount and replace it quickly and efficiently.

External PCMCIA Slot Advantages

The on-board compact flash disk is not normally populated when acquired as part of a purchased route processor. You must explicitly order a populated compact flash disk, which costs more. The external PCMCIA slots are populated by default.

In practice, most users have more flash cards in their external slots than in their on-board slots.

PRP-3 Storage Requirements

The PRP-3 has one slot of external storage available that also supports a minimum 2-GB flash disk.


Note The compact flash disks to be used with the PRP-3 are unique and cannot be interchanged with PRP-2 flash disks. Nor do PRP-3 compact flash disks work on the PRP-2.


Line Cards

The Cisco XR 12000 Series Router categorizes its line cards by engine type. Each of these line card engines has a specific feature set and performance capabilities. Cisco IOS XR currently operates only with the following line cards:

Engine 3

Engine 5

Line Card Memory

Cisco IOS XR software requires a minimum amount of memory on each line cards. Known as route memory, this is where the Cisco IOS XR software operating system resides within the line card.

This same memory stores other control plane data such as:

Routing tables

OSPF adjacencies

BFD adjacencies

Minimum Line Card Memory Requirement

To operate properly, Cisco IOS XR software requires that a line card have a minimum of 1 GB of memory.

Because not all Engine-5 and Engine-3 line cards are configured with this amount of memory, you must manually confirm the memory level of the line cards against the current minimum memory requirement before migration.

Software Audit

For information about the current minimum and recommended levels of Cisco IOS software for the Cisco IOS XR software release you want to install, see the Release Notes for that release.

Firmware Audit

For information about the minimum firmware requirements for the Cisco XR 12000 Series Router, see the Release Notes for the targeted Cisco IOS XR software release.

Audit Checklist

Table 2 lists the location of up-to-date information about the minimum levels of hardware, Cisco IOS software, and knowledge required for a successful migration

Table 2 Minimum Requirements for Migrating from Cisco IOS to Cisco IOS XR Software

Prerequisites
Locations of Latest Min. Level/Detailed Description

Minimum hardware module memory

Memory on certain hardware modules must achieve minimum capacities. See Release Notes for Cisco IOS XR Software for the current release.

Minimum line card firmware level

Line card firmware must meet the minimum levels for this release. See Release Notes for Cisco IOS XR Software for the current release.

Minimum line card memory

Line card memory must meet minimum levels for this release. See Release Notes for Cisco IOS XR Software for the current release.

Minimum ROM Monitor version level

For minimum ROM Monitor versions for the line cards and the route processor, see Release Notes for Cisco IOS XR Software for the current release.

Minimum Cisco IOS software image and Cisco IOS Boothelper versions for the current release

For the minimum Cisco IOS versions for migration to the current Cisco IOS XR software release, see Release Notes for Cisco IOS XR Software for the current release.

To access the required minimum Cisco IOS software image for the current release, see the following link (registered customers only):

http://www.cisco.com/public/sw-center/

Console access

You must have console access to route processors in the router.

TFTP knowledge

If using a TFTP server, know how to transfer files using TFTP.

Know how to set up a computer to be the TFTP server.

TFTP server file size supported

If using a TFTP server, verify whether or not your TFTP server daemon requires a patch or upgrade to support files larger than 32 MB. Install required patches or upgrade as needed.

FTP knowledge

If you plan to use FTP, you must have a basic understanding of how to transfer a file using this protocol.

You must understand how to set up a computer as the FTP server.


Migration Methodology Considerations

Migration from Cisco IOS to Cisco IOS XR software can be achieved using one of several different methods. Which method is best suited for your network migration depends on the preferences and resources available to support the migration.

These methods (shown in Figure 1) consist of variations on two strategies:

Direct migration—Turboboot

Pre-staged migration:

Disk swapping

RP swapping

A combination of the foregoing is also possible. For example, you can Turboboot a spare RP in the laboratory and then upgrade the production router by exchanging a Cisco IOS RP with a Cisco IOS XR RP.

The distinction between the two principal strategies has to do with whether an existing router is migrated in place, or whether parts of the migration can be performed within an offsite facility before the final migration occurs.

Although some variations may exist within the execution of each strategy, the principles remain the same.

Figure 1 Migration Methods

Direct Migration

Using this method, you remove the target router and its line cards from service to perform the necessary hardware upgrades and software migration while still connected to the production network. To take the router out of service, you can, for example, adjust the route-metrics to make the router less preferred, shut down interfaces, or shut down the router itself.

When upgrading hardware components, this migration methodology includes swapping old hardware with new hardware (such as swapping PRP-2 with PRP-3) and booting the new hardware in place. This allows the system to detect the new hardware and execute the software operations (such as preparing the disk) needed for a live system to operate.

When migrating from Cisco IOS to Cisco IOS XR software, you, likewise, take the router out of service to perform the Turboboot procedure needed to migrate toCisco IOS XR software.

Direct migration methodology is probably the safest method to choose, because it allows you to avoid some of the negative byproducts of upgrading or migrating a system that has already been placed into production. For example, when you use the direct migration method, the environment variables used to boot the system are selected for the user as part of the process. However, if you use other migration methods, you must make sure to set these environment variables manually. Otherwise, your system will not boot properly.

On the other hand, if the amount of downtime and effort required to complete direct migration are an issue, this method may not be the best choice.

Pre-staged Migration

This strategy is useful when you do not have onsite operators who can perform the direct migration locally. It is also the best choice when downtime is an issue, because a direct migration can take approximately one hour.

Pre-staging primarily has two benefits:

Less Downtime—The downtime associated with the migration is minimized to the amount of time it takes to swap the Cisco IOS hardware with the Cisco IOS XR hardware and to reboot the router. The bulk of the OS preparation occurs before the migration maintenance window and consumes no downtime during the preparation efforts.

Easy to Back Out If Problems Arise—Should an issue arise, you can simply reverse the process, using the back-out procedure. This consists of removing the Cisco IOS XR-based hardware and reinstalling the Cisco IOS-based hardware. The Cisco IOS configurations then still exist on the Cisco IOS hardware and can be returned to service quickly if need be.

Pre-staged Migration Process

Pre-staging involves upgrading hardware within a laboratory environment before the actual migration of the production node, often followed by pre-installing the Cisco IOS XR operating system onto the disk before shipment to the field. The strategy behind the pre-staging is to prepare a number of RPs or flash disks in advance and then ship them to the remote point of presence (POP) where the upgrade or migration should take place.

Variations in this method extend to which hardware part is pre-staged (for example, flash disk versus the route processor itself), as well as to where the staging is performed (onsite versus offsite).

Also, by using some of the built-in Cisco IOS XR utilities to help prepare the RPs or flash disks, you run less risk of encountering unforeseen issues, because these utilities are part of Cisco IOS XR software.

Optionally, you may also choose to preconfigure the final Cisco IOS XR configuration file. This reduces the actual cutover procedure to removing the Cisco IOS-based RP or disk and installing the Cisco IOS XR-based RP or disk.

Pre-staged migrations consist of:

Disk Swapping

Performance Route Processor Swapping

Disk Swapping

Disk swapping consists of the following sub-strategies:

Golden Disk (disk backup)

Disk Mirroring

Disk Cloning

Golden Disk

This method uses a specific feature of Cisco IOS XR software called Golden Disk to replicate the disk. A system backup disk is created whenever you back up the system files to a local storage device for the first time. This process formats the selected device, and copies the software packages and system configurations to that device.

Afterwards, you boot the target system using the newly created disk.


Note After the Golden Disk feature is enabled, you cannot configure disk mirroring.


Disk Mirroring

Disk mirroring replicates critical data on the primary boot device on another storage device on the same RP, creating redundancy. If the primary boot device were to fail, the Cisco IOS XR operating system would continue to operate on the secondary device.

Disk mirroring avoids having to to switch over to a standby RP in the event that the primary storage device fails. In the event that a primary storage device fails, you can replace or repair it without disrupting service.

Disk mirroring normally only mirrors critical data from the primary boot device onto a secondary storage device. Logging data would, for example, be considered noncritical.

You can use disk mirroring to create Cisco IOS XR seed disks for Cisco IOS XR migration, which you can then move to your target networks to boot Cisco IOS XR software.


Note After disk mirroring is enabled, you cannot configure the Golden Disk feature.


Disk Cloning

Disk cloning refers to the creation of a binary copy of a working Cisco IOS XR disk that you copy to a target disk by using either Cisco or third-party utilities. For example, you can replicate a disk by using MS Windows, UNIX, or Linux machines equipped with flash disk readers. You use these binary copies as seed Cisco IOS XR disks that you can install into the target networks, so that they boot Cisco IOS XR software.

For the purposes of disk cloning, the target disk must be formatted using the FAT16 file system for any Cisco IOS XR releases prior to Release 3.8.0. Cisco IOS XR Software Release 3.8.0 and later releases require the target disk format to use the FAT32 file system.

Some Cautions Concering Disk Cloning

When you clone the disk, you also copy the running configuration from the staging router to potentially apply it to the target router. Therefore, consider performing one of the following actions:

Erase all configurations on the staging router before cloning.

Load any desired confiurations onto the staging router before cloning.

Erase the configurations on the target device after booting up, and configure the router from scratch.

Performance Route Processor Swapping

Using the performance route processor (PRP) swapping technique, a complete Cisco IOS XR-ready PRP is swapped into the target system instead of a prebuilt Cisco IOS XR disk.

PRP pre-staging involves preparing the PRP in a staging environment with the correct Cisco IOS XR release and to, optionally, pre-configure the PRP with your desired configuration. The pre-staged PRP is then shipped to the target production site and the migration is performed by swapping out the Cisco IOS-configured PRPs with the preconfigured Cisco IOS XR PRPs.

This method reduces downtime for the target router to the time it takes to power down the router, change the hardware, power up the system, and wait for the router to complete the boot process.


Timesaver If you are considering migration from PRP-2-based systems to PRP-3-based systems at the same time as your migration to Cisco IOS XR, PRP swapping lets you combine a PRP upgrade with an operating system migration in one effort.


There are two ways of pre-staging the PRP:

Turbobooting Cisco IOS XR onto the target PRP in a staging environment.

Pre-staging a Cisco IOS XR disk (using one of the disk replication methods already described) and inserting that disk into the target PRP before shipment to the target destination.

Pre-staging Strategy Comparison

Table 3 summarizes the differences between the two pre-staging strategies. The aim of pre-staging is to reduce the time needed during the maintenance window to perform critical, but time-consuming tasks (installation of operating system, optional packages, and target configuration) associated with migration by shifting these activities outside of that timeframe.

Both methods share the advantage that they eliminate the need to use Turboboot, and each method requires that a staging facility be available for the purpose.

Table 3 Comparison of Pre-staging Methods

Disk Swapping
PRP Swapping

Requires you enter ROMMON during the critical period.

Does not require you enter ROMMON during the critical period.

Requires that BOOT variable be set during the cutover maintenance window.

Does not require that BOOT variable be set during the cutover maintenance window; the BOOT variable is instead set during the pre-staging phase.

Requires spare flash disks.

Requires spare PRPs populated with flash disks.

Packaging and shipping are relatively easy.

Requires care in packaging and shipping.

Ideal approach when target disks also require an upgrade.

Ideal approach when target PRPs also require an upgrade.


Table 4 compares the different disk replication procedures used for pre-staging the target disk.

Table 4 Comparsion of Disk Replication Procedures

 
Rel. Introduced
What Is Replicated?
Disk Partitioning Needed?
Time Needed to Complete
(approx. min.)
Device Supported
Key Benefit
Golden Disk

3.4.1

All disk content.

No

25-35

Disk0:, Disk1:, and compact flash disk.

Replicates freshly Turbobooted disk without needing to partition.

Disk Miroring

3.6.0

Only critical files used by the system (logs not replicated).

Yes

30

Disk0:, Disk1:, and compact flash disk (PRP-3)

Replicates disk from a working system, but without unnecessary files.

Replicates disk without a router reboot.

Disk Cloning 1

3.2

All disk content by default. Selective copy also possible.

No

20

Disk0:, Disk1:, and compact flash disk.

Flexibility to copy files selectively.2

Disks can be replicated outside of Cisco IOS XR.

1 Disk cloning, or disk replication, uses the Cisco IOS XR shell and can actually be achieved by a variety of methods; for example, a Cisco IOS XR cp command, a third-party tool, or other techniques. For this reason, it is difficult to compare disk cloning to other methods, because it is not a single method.

2 This is also its disadvantage, because it can cause problems if the correct files are not copied.


Comparison of Direct and Pre-staged Migration Stategies

Table 5 illustrates important differences between each of the migration strategies. Keep in mind that no one strategy suits every situation. Your choice should be based on the issues that make sense given your particular network.

Table 5 Comparisons of Migration Strategies 

Direct Migration (Turboboot)
Disk Swapping 1
PRP Swapping

No spare disks or RP cards are needed.

Requires spare disks.

Requires spare PRPs populated with disks.

No lab router is needed.

Lab router is needed only for the very first disk for replication.

Requires a lab router for pre-staging the PRP.

Requires setting the boot variable during the pre-staging phase.

Upgrade downtime incorporates time needed to configure ROMMON variables settings, TFTP transfer, Turboboot, and reload.

Upgrade downtime incorporates time needed to physically swap disks, setting ROMMON variables, and reloading.

Upgrade downtime incorporates time needed to physically swap the PRP and reload it.

Can be done remotely.

Requires someone to be on site.

Requires someone to be on site.

No shipping is required.

Easily shipped. Disks can be hand-carried to site, as well.

Requires special packaging and shipment handling.

Requires more complex procedures to avoid electrostatic discharge.

Cleans disk and system files if the master copy is prepared using the format option with Turboboot procedure.

Cleans disk and system files if the master copy is prepared using the format option with Turboboot procedure.

Requires disk reformatting if PRP is pre-staged using the Turboboot procedure.

Upgrading disks during the maintenance window cannot be combined with the Turboboot procedure. The disk upgrade must be performed separately.

Upgrading disks can be included with the migration during the maintenance window.

Upgrading disks can be included with the migration during the maintenance window.

Upgrading PRPs costs more time during the maintenance window.

Upgrading PRPs costs more time during the maintenance window.

Upgrading PRPs does not cost more time during the maintenance window.

1 Includes Golden Disk backup, disk mirroring, and disk cloning.


Scheduling the Operating System Cutover

Upgrades performed in preparation for migration to the Cisco IOS XR operating system can technically be performed weeks in advance of the cutover, or they can be deferred until the actual maintenance window in which the cutover will occur. Table 6 illustrates some pros and cons to each approach.

Performing the upgrades in advance of the Cisco IOS XR migration allows the network to be prepared in an orderly fashion. The ultimate goal is for the cutover from Cisco IOS to Cisco IOS XR software to occur as accurately and quickly as possible, and to ensure that the migration succeeds.

Cisco migration deployment teams have found that when too many operations occur within the same maintenance window, it creates a greater risk that other problems may occur. For example, if you experienced any difficulty in replacing memory modules, this could create a delay within the maintenance window. That delay could then cause yet other problems during the operating system cutover that reduced the amount of time available to recover from any unforeseen issues.

As a result, we strongly recommend that you complete multiple network audits, all required upgrades, and a final audit following the upgrades before you cut over to the Cisco IOS XR operating system.

This recommendation is especially important if any of your audits show that you need to make any physical changes to the router (such as memory upgrades or line card replacements). Physical upgrades can add considerable complexity and risk to the migration if they are conducted at the same time as the Cisco IOS XR operating system cutover.

Table 6 Considerations for Scheduling the Upgrades

 
When to Perform Required Upgrades
Pro
Con
 
Before the cutover

Minimizes the duration and complexity of the actual cutover window.

Allows the network to stabilize

Requires more planning and time.

Requires extra audits of the network.

 
Within the maintenance window for the cutover

Requires only one visit per router.

All operations are performed on a given router on the same day.

Requires more time during the cutover window.

Adds complexity to the cutover window.

If problems occur, can greatly extend time of cutover due to troubleshooting and recovery efforts.


How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software


Note The audit and upgrade of your system may take up to 40 minutes, depending on how many elements in your network may require an upgrade.


Before migrating to the Cisco IOS XR software, you must verify each node in the network against the requirements listed in Table 2: "Minimum Requirements for Migrating from Cisco IOS to Cisco IOS XR Software" and perform an upgrade, where necessary.

The network audit and upgrade of its components consist of the following tasks:

Verifying Your Cisco IOS Image (required)

Verifying Cisco IOS Boothelper (required)

Verifying Cisco ROM Monitor (required)

Verifying Line Card Firmware (required)

Verifying Line Card Physical Memory (required)

For code examples, see How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software: Examples.

Verifying Your Cisco IOS Image

If the Cisco IOS image on your router does not meet the requisite level for the migration to Cisco IOS XR software in the current release, you must upgrade. For Cisco IOS upgrade procedures, refer to the Cisco IOS Upgrade Planner link accessible from http://www.cisco.com/public/sw-center/.

To verify which image you are running, enter the show version command.

Verifying Cisco IOS Boothelper

Cisco IOS Boothelper software extends the capabilities of Cisco ROM Monitor on a Cisco XR 12000 Series Router:

With Boothelper, ROM Monitor can load images from flash memory and TFTP servers.

Without Boothelper, ROM Monitor can load images only from a local storage device (Disk0, Disk1, and boot flash memory).

Before you can use Cisco IOS Boothelper to connect to remote devices such as a TFTP server, you must configure the Management Ethernet interface in the Boothelper software.


Caution You cannot start Cisco IOS software or Cisco IOS Boothelper on one RP in a chassis if Cisco IOS XR software is running on the other RP.

We recommend that you upgrade and configure Cisco IOS Boothelper to the minimum level on all RPs, if needed, before starting the first one with Cisco IOS XR software installed. (For the minimum Cisco IOS Boothelper level, see Cisco IOS XR Software Release Notes for the current Cisco IOS XR software release.)


Timesaver If IP connectivity is already established, you can skip Step 2 (configure terminal) through Step 7 (exit).



Note Completion can take up to 10 minutes.


SUMMARY STEPS

1. dir bootflash:

2. configure terminal

3. ip default-gateway server-address

4. interface type number

5. ip address server-address mask

6. no shutdown

7. exit

8. copy running-config startup-config

9. show interface type instance

10. ping server-address

11. delete bootflash: filename

12. squeeze bootflash:

13. copy tftp://server-address/bootfile/ bootflash:

or

copy ftp://username:password@ftpAddress/bootfile bootflash:

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

dir bootflash:

Example:

Router# dir bootflash:

Lets you verify the level of the Cisco IOS Boothelper version on the router.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters Cisco IOS configuration mode.

Step 3 

ip default-gateway server-address

Example:

Router(config)# ip default-gateway 192.168.16.23

Defines a default gateway (router) when IP routing is disabled.

In this case, the value of server-address must be the address of the TFTP server or default gateway router and must be in the same network as the address on the management port.

Step 4 

interface type number

Example:

Router(config)# interface Ethernet0

Enters interface configuration mode and specifies the Management Ethernet name and designation.

Step 5 

ip address server-address mask

Example:

Router(config-if)# ip address 192.168.16.1 255.255.255.0

Configures the management port to communicate with the TFTP server or default gateway router.

Note If you are loading images from a network, each route processor management port requires a unique IP address.

Step 6 

no shutdown

Example:

Router(config-if)# no shutdown

Removes the shutdown configuration on the interface, enabling it to move to the up state or the down state. This ensures that the interface remains in an administratively operational state (up).

Step 7 

exit

Example:

Router(config)# exit

Exits global configuration mode.

Step 8 

copy running-config startup-config

Example:

Router# copy running-config startup-config

Saves the running configuration changes to NVRAM.


Caution If you do not save the running configuration to NVRAM, your configuration settings are lost the next time you reload the router.

Step 9 

show interface type instance

Example:

Router# show interface Ethernet0

Verifies that the interface for access to the TFTP or FTP server is functional.

Step 10 

ping server-address

Example:

Router# ping 192.168.16.1

Pings the TFTP or FTP server to assure that you have network connectivity before performing the TFTP or FTP operation.

Step 11 

delete bootflash: filename

Example:
Router# delete bootflash:xyz

Deletes the existing Cisco IOS Boothelper image.

Step 12 

squeeze bootflash:

Example:

Router# squeeze bootflash:

Removes deleted files from the flash disk and creates space. This is analogous to disk defragmentation.

Step 13 

copy tftp:bootflash:server-address/bootfile/

or

copy ftp://username:password@ftpAddress/bootfile bootflash:

Example:
Router# copy tftp: bootflash:Address or name of 
remote host [192.168.16.1]?

Copies the new Cisco IOS Boothelper image file to the boot flash disk from either a TFTP or an FTP server.

Options:

copy tftp: bootflash:—Launches a dialog to copy a file from a TFTP server to the online flash memory SIMM (boot flash memory). The router then queries for the IP address, source file, and destination file.

copy ftp://username:password@ftpAddress/bootfile bootflash:—Copies the filename to the boot flash memory.

Verifying Cisco ROM Monitor

To prevent otherwise avoidable problems, review the prerequisites listed in the "Prerequisites for Migration" section.


Caution Because this procedure involves a restart and disruption of service, you should perform these steps from the console port within a maintenance window.


Note Completion can take up to 10 minutes.


SUMMARY STEPS

1. show diags | include SLOT | ROM Monitor

2. upgrade rom-monitor slot primary-slot force

3. upgrade rom-monitor slot secondary-slot force

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show diags | include SLOT | ROM Monitor

Example:

Router(admin)# show diags | include SLOT | ROM Monitor

Lets you verify your current ROM Monitor version on the installed route processor cards against the minimum requirements.

If the version is earlier than the minimum specified version in Release Notes for Cisco IOS XR Software, you must upgrade ROM Monitor.

Step 2 

upgrade rom-monitor slot primary-slot force

Example:

Router(admin)# upgrade rom-monitor slot-0 force

Upgrades ROM Monitor on the primary RP.

Step 3 

upgrade rom-monitor slot secondary-slot force

Example:

Router(admin)# upgrade rom-monitor slot-1 force

Upgrades ROM Monitor on the secondary RP.

Verifying Line Card Firmware


Note Completion can take up to 20 minutes, including the restart of the line cards.



Caution Make sure you upgrade the firmware on the relevant line card to the appropriate level before you upgrade the physical memory of the line card. Otherwise, the line card will not boot after Cisco IOS XR software migration. If this scenario occurs, the only way to resolve it is to reverse the physical memory installation and then reload Cisco IOS software onto the router to perform the required firmware update.

The process for upgrading the line card firmware is as follows:

Verify the line card firmware level against the requirements listed in Release Notes for Cisco IOS XR Software for the target release.

Verify that you are running the correct version of Cisco IOS software by comparing the version running on the routers to the minimum version documented in Release Notes for Cisco IOS XR Software for the target release.

Upgrade line card firmware, as needed.


Caution Upgrades are potentially disruptive to service.

SUMMARY STEPS

1. show diags | inc SLOT| MBUS | Fabric Downloader

2. show version

3. upgrade all all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show diags | inc SLOT| MBUS | Fabric Downloader

Example:

Router# show diags | inc SLOT | MBUS | Fabric Downloader

Displays the firmware version of each card installed in the router.

Step 2 

show version

Example:

Router# show version

Verifies which release of Cisco IOS software you are running.

Step 3 

upgrade all all

Example:

Router(admin)# upgrade all all

Upgrades the line card firmware with the most recent version on the RPs.


Caution Upgrade is potentially disruptive to service.

Verifying Line Card Physical Memory


Note Duration for completion depends on user familiarity with uninstalling and reinserting line cards.


For instructions on uninstalling and reinserting memory modules from the Cisco XR 12000 Series Router chassis, see Cisco 12000 Series Router Memory Replacement Instructions.


Caution Do not upgrade the physical memory of the line cards before you have upgraded the line card firmware or your migration will fail. For more information, see Verifying Line Card Firmware.

SUMMARY STEPS

1. show diags location slot | inc Memory

2. (Optional) Add memory as needed by removing the line cards, adding the required memory, and reinserting the line cards into the chassis.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show diags location slot | inc Memory

Example:

Router# show diags location 0/2/cpu0 | inc Memory

Mon Jun 1 05:23:11.017 PST

Route Memory: MEM-LC5-2048=

Packet Memory: MEM-LC5-PKT-512=

Displays the memory configuration of each card installed in the router.


Caution Before you migrate the system to Cisco IOS XR software, you must have the minimum required memory on the line cards. Otherwise, the migration cannot succeed. You must then reinstall the required minimum level of Cisco IOS software; upgrade the line card firmware, as needed; and then install the line card memory. To upgrade the line card firmware, see the "Verifying Line Card Firmware" section.

Step 2 

Remove the line cards and add any required memory. Reinstall the line cards in the chassis.

(Optional) Upgrades the line card memory to the minimum required.


Caution Before you add additional memory to the line card, you must update the firmware, if necessary. See the "Verifying Line Card Firmware" section.

For information about uninstalling and reinstalling memory modules on the Cisco XR 12000 Series Router, see Cisco 12000 Series Router Memory Replacement Instructions.

How to Perform a Direct Migration

Direct migration, also known as the Turboot method, installs Cisco IOS XR software on the router in place, as opposed to staging parts of the installation ahead of the actual OS cutover.


Caution The migration from Cisco IOS to Cisco IOS XR software can take from 1 to 3 hours and causes a disruption in service. Be sure to schedule the migration within a maintenance window.

Direct migration requires review and execution of the following:

Prerequisites for Direct Migration (required)

Restrictions for Direct Migration (required)

Preparing the Target Device (required)

Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router (required)

How to Perform a Pre-staged Migration (optional)

Troubleshooting a Failed Migration (optional)

Prerequisites for Direct Migration

You must identify a target device for the router. This is the local disk on the route processor (RP) where the software is installed. On the Cisco XR 12000 Series Router, the supported target devices for this purpose are disk0:, disk1:, or compactfash:.


Note We recommend that you install to disk0:. Disk 0 is preinstalled in most RPs, ensuring that the correct disk is used to store the software packages on the entire system.


You should have made a backup copy of your Cisco IOS image to disk1:, if you have one installed, before you install Cisco IOS XR software.

Both the primary and standby route processors must be brought into ROMMON mode simultaneously.

You must have the downloaded the tar file for the target release to your machine and untarred it. This contains the Cisco IOS XR software images c12k-mini.vm and mbiprp-rp.vm , which should have been moved to the intended flash disk, TFTP, or FTP server.


Note The image c12k-mini.vm is for the primary route processor and mbiprp-rp.vm is for the standby route processor only.


These images should be on the target devices to make the images available for steps you perform later on, as described in the "Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router" section.

Restrictions for Direct Migration

You cannot add Cisco IOS XR software packages to any other location than the original target device. For example, you cannot install the base operating system to disk:1 and then add other software packages to disk:0. In other words, all software packages must be installed to the same slot where you installed the operating system.

You cannot remove the installation disk after you have booted the Cisco IOS XR software and while the system is running. Otherwise, your system may fail and your disk may be corrupted. Always power down the system before you remove the installation disk.

Preparing the Target Device

We strongly recommend that you use the following procedure to reformat the target device in preparation for the installation of Cisco IOS XR software.


Caution If important files reside on the target device, you should archive them to an offline storage device now.

SUMMARY STEPS

1. format target-device

2. dir target-device

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

format target-device
Example:
Router# format disk0:

Reformats the target device, eliminating all files that may reside there, and ensuring that the device has the appropriate file system.


Caution Be sure that you use either the minimum version of Cisco IOS Boothelper referenced in the Release Notes for the current release or a later version.

Step 2 

dir target-device

Example:

Router# dir disk0:

Verifies that the target device has been cleaned.

Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router

This procedure installs Cisco IOS XR software onto your primary and standby route processor (RP), if you have a standby. If you do not have a dual-RP router, disregard the steps for the standby.

Before you start, make sure you have reviewed the "Prerequisites for Migration" section and the "Restrictions for Migration" section.

For examples of the code entered and returned during the migration process, see the "Installing Cisco IOS XR Software on the Primary RP: Example" section.


Caution Do not delete the Cisco IOS configuration from NVRAM, because this configuration is necessary for booting an image using FTP or TFTP.


Note Installation can take up to 90 minutes.


SUMMARY STEPS

Perform the following steps in Cisco IOS on both the primary and the standby RP, if you have one.

1. configure terminal

2. config-register 0x0

3. exit

4. write memory

Perform the following steps in ROMMON mode on the primary RP.


Timesaver To save time, consider performing Step 5 to Step 12 in parallel with Step 13to Step 18 on your primary and standby RPs.


5. reload

6. unset BOOT

7. TURBOBOOT=on,target-device

8. sync

9. reset

10. set

11. boot tftp://server-address/path/bootfile or boot ftp://username:[password]@server-address/


Note You can insert a standby RP when the primary RP is up and runing. Once the standby RP boots up, it synchronizes with the primary RP and comes up with all the the packages and Software Maintenance Units (SMU)s.


Perform the following steps in ROMMON mode on the standby RP, if you have one.

12. unset BOOT

13. unset TURBOBOOT

14. sync

15. reset

16. set

17. boot tftp://server-address/path/bootfile or boot ftp://username:[password]@server-address/bootfile

Perform the following steps in the Cisco IOS XR operating system on the primary RP after router startup.

18. root-system-username

19. root-system-username-password

20. show install summary

21. show platform

22. show diags

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 2 

config-register 0x0

Example:

Router(config)# config-register 0x0

Changes the Configuration Register Boot field settings.

Note Setting the value to 0x0 requires a manual restart of the operating system using the boot command.

Step 3 

exit

Example:

Router(config)# exit

Exits global configuration mode.

Step 4 

write memory

Example:

Router# write memory

Saves your settings.

 
Perform the following steps in ROMMON mode on the primary RP:
 

Step 5 

reload

Example:

Router# reload

Restarts the route processor in ROMMON mode.

Step 6 

unset BOOT

Example:

rommon 1># unset BOOT

Clears the router monitor BOOT variable.

Step 7 

TURBOBOOT=on,target-device,format

Example:
rommon 2># TURBOBOOT=on,disk0,format

Sets the environment variable to indicate that installation should take place on the target device (Disk0, Disk1, or Compact Flash) and formats the target device.

Step 8 

sync

Example:

rommon 3># sync

Writes the monitor environment variables to NVRAM.

Step 9 

reset

Example:

rommon 4># reset

Resets the router.

Step 10 

set

Example:

rommon 5># set

Verifies that the IP addresses assigned to the Ethernet interfaces are correct.

Step 11 

boot tftp://server-address/path/bootfile

or

boot ftp://username:[password]@server-address/
bootfile

Example:

rommon 5># boot tftp:// 192.168.1.1/sky2dir/c12k-mini.vm-3.8.0

or

rommon 5># boot ftp://iprem:pwd@192.85.16.23//
c12k-mini.vm-3.8.0

Starts and installs the Cisco IOS XR software image specified.

Note The example shows the image file for the primary RP only.

Note Step 11 takes about 40 minutes to complete, including the reboot operation, in which copies are made to disk.

 
Perform the following steps in ROMMON mode on the standby RP, if you have one:
 

Step 12 

unset BOOT

Example:

rommon 6># unset BOOT

Clears the router monitor BOOT variable.

Step 13 

unset TURBOBOOT

Example:

rommon 7># unset TURBOBOOT

Clears the TURBOBOOT monitor variable.

Step 14 

sync

Example:

rommon 8># sync

Writes the monitor environment variables to NVRAM.

Step 15 

reset

Example:

rommon 9># reset

Resets the router.

Step 16 

set

Example:

rommon 10># set

Verifies that the IP addresses assigned to the Ethernet interfaces are correct.

Step 17 

boot tftp://server-address/path/bootfile

or

boot ftp://username:[password]@server-address/
bootfile

Example:

rommon 11># boot tftp://192.168.1.1/sky2dir/ mbiprp-rp.vm-3.8.0/

or

rommon 11># boot ftp:user://pwd@192.85.16.23// mbiprp-rp.vm-3.8.0/

Starts the program on the image file that copies all the software packages from the primary to the standby RP.

Note mbiprp-rp.vm-3.8.0/ is the image file for the standby RP only.

Note Step 17 takes about 40 minutes to complete, including the reboot operation, in which copies are made to disk.

 
Perform the following steps in Cisco IOS XR software on the primary RP after the TURBOBOOT process finishes:
 

Step 18 

root-system-username

Example:

RP/0/0/CPU0:Enter root-system username: admin

Creates an administrative user.

Step 19 

root-system-username-password

Example:

RP/0/0/CPU0:Enter secret: <admin>

Creates a password for the administrative user.

Step 20 

show install summary

Example:

RP/0/0/CPU0:Router# show install summary

Verifies the software installed on the primary RP.

Step 21 

show platform

Example:

RP/0/0/CPU0:Router# show platform

Verifies that Cisco IOS XR software is running on the RPs, line cards, and SPAs. RPs and line cards should be in the IOS XR run state, and SPAs should be in the ready state.

This may take several minutes.

Tip The length of time it takes after the router restarts before the status is final and the line cards are in the run state depends on the number of line cards installed in the chassis.

Step 22 

show diags

Example:

RP/0/0/CPU0:Router# show diags

Shows firmware revision numbers and other details for verification that the line card firmware is at the minimum operating level for Cisco IOS XR software.


Caution If your output contains the code line: Getting ROM Response (ROM  VGET), see Symptom   4 of "Troubleshooting a Failed Migration" on page 37.

How to Perform a Pre-staged Migration

Pre-staged migration methods have their own prerequisites and restrictions and can be performed in a variety of ways, as described in the sections that follow:

Prerequisites for Pre-staged Migrations

Restrictions for Pre-staged Migrations

Swapping Disks

Creating a Disk Backup with a Golden Disk

Mirroring a Disk

Cloning a Disk

Swapping a PRP

Prerequisites for Pre-staged Migrations

These pre-staged migration methods have the following prerequisites:

Disk cloning—If using disk cloning, you must have formatted the disk to the appropriate FAT file system. If using disk cloning to replicate Cisco IOS XR software older than Release 3.8.0 onto disks, format the disk to the FAT16 file system.

This implies that the maximum disk space supported is 2 GB, because FAT16 cannot address more than 2 GB of address space). Starting with Release 3.8.0, Cisco IOS XR software supports 4-GB flash disks using the FAT32 file system.

Disk mirroring—If using disk mirroring, make sure that the target disk is the same size as or greater than the source disk.

Rebooting line cards (all methods)—It is important that line cards be rebooted when performing the migration. Therefore, it is a good practice to power down the router during the migration, because this automatically resets the RP and causes all the line cards to be rebooted and to run the proper Cisco IOS XR software images.

If the line cards fail to reboot, you can force a reload of all of the line cards after the RP is running Cisco IOS XR software; use the hw-module location path-id reload command in administration EXEC mode.


Caution If the line cards are not rebooted either through a power-down of the RP or a manual reset, you may find that you have an RP that is running Cisco IOS XR software, but line cards that are still running Cisco IOS software. This, in turn, can cause inconsistent communications between the RP and the line cards.

Restrictions for Pre-staged Migrations

These pre-staged migration methods have the following restrictions:

You cannot add Cisco IOS XR software packages to any other location than the original target device. For example, you cannot install the base operating system to disk:1 and then add other software packages to disk:0. In other words, all software packages must be installed to the same slot where you installed the operating system.

You cannot remove the installation disk after you have booted the Cisco IOS XR software and while the system is running. Otherwise, your system may fail and your disk may be corrupted. Always power down the system before you remove the installation disk.


Note If you make copies using either the Golden Disk backup or mirroring techniques, you can turn these utilities off before unmounting the disk and removing it.


All pre-staged migration methods are mutually exclusive—After you have enabled one type of pre-staged migration method, you cannot use another. Therefore, analyze the advantages and disadvantages of each migration method carefully before making a decision on which to use. However, it is perfectly fine to use one method to clone an installation disk, but another method later on to clone the copy.

Golden Disk Backup—When you run the Golden Disk backup feature from within SDR EXEC mode, it only replicates the files from that specific SDR. It does not replicate every file needed for migration.


Note To replicate all of the files from the administration location and from each SDR, perform the Golden Disk backup from within administration EXEC mode.


Swapping Disks

Disk swapping is a subclass of the pre-staged methodologies. Instead of Turbobooting each system individually, you pre-initialize flash disks in a staging facility to contain the intended Cisco IOS XR software release, any optional packages, and configuration files. Afterwards, during the scheduled migration maintenance window, you swap the existing Cisco IOS disk for a Cisco IOS XR disk, then start the system up in the Cisco IOS XR operating system.


Timesaver When you require specific configurations on multiple nodes, clear any existing configurations on the seed disk by using the commit replace command and preconfigure it with the features you want to seed onto your target nodes.


SUMMARY STEPS

1. On a staging router in a laboratory, prepare the disk to be used for disk swapping:

a. Use the Turboboot procedure to prepare a disk. See Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router.

b. Make a copy of the working disk on the target disk using either the Golden Disk, disk mirroring, or disk cloning methods.

On the target PRP:

2. configure terminal

3. config-register 0x00

4. exit

5. write memory

6. Power off the router.

7. Swap the pre-staged Cisco IOS disk with a disk containing the new Cisco IOS XR software image.

8. Power on the router.

9. unset BOOT

10. unset TURBOBOOT

11. BOOT=device:directory/image

12. sync

13. reset

14. boot device:directory/image

On the standby RP:

15. Keep the standby RP in ROMMON mode until the PRP has booted successfully and shows that it is in the Cisco IOS XR RUN state; repeat Steps 9. through 14. on the standby RP.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

On a staging router in a test laboratory:

a. Use the Turboboot procedure to prepare a disk. See Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router.

b. Make a copy of the working disk on the target disk using either the Golden Disk, disk mirroring, or disk cloning methods.

See Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router.

Note You can also turboboot a seed disk and then copy its contents to multiple disks by means of the Golden Disk backup, disk mirroring, or disk cloning to be used in the pending migration.

Step 2 

configure terminal

Example:

Router# configure terminal

Takes place on the target PRP.

Enters terminal configuration mode to enable terminal registration configuration.

Step 3 

config-register 0x00

Example:

Router(config)# config-register 0x00

Changes the Configuration Register Boot field settings.

Step 4 

exit

Example:

Router(config)# exit

Exits global configuration mode.

Step 5 

write memory

Example:

Router# write memory

Saves your settings.

Step 6 

Power off the router.

Step 7 

Swap the pre-staged Cisco IOS disk with a disk containing the new Cisco IOS XR software image.

Step 8 

Power on the router.

Step 9 

unset BOOT

Example:
rommon1# unset BOOT

Clears the router monitor BOOT variable.

Step 10 

unset TUROBOOT

Example:
rommon2# TURBOBOOT

Clears the router monitor TURBOBOOT variable.

Step 11 

BOOT = device:directory/image,priority;

Example:

rommon3# BOOT=disk0:
c12k-os-mbi-3.8.1/mbiprp-rp.vm

Sets the environment variable to indicate that installation should take place on the target device (Disk0, Disk1, or Compact Flash) and formats the target device.

You should modify the BOOT variable, so that it points to the desired minimum boot image (MBI) file on the new disk.

You may, optionally, reset the configuration register back to 0x2102 at this stage.

Note This BOOT variable is different from the TURBOBOOT variable described elsewhere in this document.

Step 12 

sync
Example:
rommon4# sync

Writes the monitor environment variables to NVRAM.

Step 13 

reset

Example:
rommon5# reset

Resets the router.

Step 14 

boot  device:directory/image
Example:
rommon6# boot disk0: 
c12k-os-mbi-3.8.1/mbiprp-rp.vm

Loads the desired Cisco IOS XR software image onto the router.

Step 15 

Keep the standby RP in ROMMON mode until the PRP has booted successfully and shows that it is in the Cisco IOS XR RUN state; repeat Step 9 through Step 14 on the standby RP.

Creating a Disk Backup with a Golden Disk

This method creates a system backup disk whenever you back up the system files to a local storage device for the first time. The process formats the selected device, and copies the software packages and system configurations to that device.

If the backup operation is performed from within EXEC mode, then only the files from that specific secure domain router (SDR) are backed up. If the backup operation is performed from within administration EXEC mode, then the files from the administration plane and all of the SDRs are backed up.

After a backup disk is created using the Golden Disk, that backup disk is then removed from the staging system and is inserted into the target system. The target system is then booted using the newly created disk.


Tip When making a golden disk, you do not have to power off the router and then power it back on each time a copy is made. Instead, just disable the mirroring or disk backup utility, and unmount and then remove the disk.


For more information on using the Golden Disk feature to implement a pre-staged migration see Creating a Disk Backup for Cisco IOS XR Software and Configurations in Cisco IOS XR System Management Configuration Guide.

SUMMARY STEPS

1. (Optional) admin

2. (Optional)show system backup [target-dev] [details | diff] [location {all | node-id}] [verify]

3. (Optional) system boot-sequence {primary-device [secondary-device]} [location {all | node-id}]

4. (Required)system backup [target-dev] [format] [location {all | node-id}] [synchronous | asynchronous]

5. (Optional) Repeat Step 2.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/CPU0:Router:# admin

(Optional) Enters administrative EXEC mode.

Backs up the files from the administration plane and includes all of the SDRs.

Step 2 

show system backup [target-dev] [details | 
diff] [verify] [location {all | node-id}]
Example:

RP/0/CPU0:Router(admin):# show system backup disk0: detail

(Optional) —Displays backup details and history.

Step 3 

system boot-sequence {primary-device 
[secondary-device]} [location {all | 
node-id}]
Example:

RP/0/CPU0:Router(admin):# system boot-sequence disk0: disk1:

Info: node0_0_CPU0: command succeeded.

(Required) Formats the primary and secondary boot devices and copies the software and configurations from the source to the target disk .

In this example, the software and configurations located on disk0 are copied to disk1.

Step 4 

Repeat Step 2.

(Optional) —Shows the results from Step 3.

Mirroring a Disk

Disk mirroring is another form of pre-staged migration that uses this feature of Cisco IOS XR software to replicate the seed disk. The duplicate disks can then be moved to the target systems to enable them to boot Cisco IOS XR software.

Disk mirroring replicates the critical data on the primary boot device onto another storage device (secondary location) on the same RP. If the primary boot device were to fail, then Cisco IOS XR applications continue to be serviced transparently by the secondary device.

This mechanism normally avoids a switchover to the standby RP, should the primary storage device fail. The failed primary storage device can then be replaced or repaired without disruption of service.


Note Disk mirroring normally only mirrors critical data from the primary boot device onto a secondary storage device. An example of non-critical and, therefore, non-mirrored data would be logs.


For more information about disk mirroring, see Cisco IOS XR System Management Configuration Guide.

SUMMARY STEPS

1. format secondary-device partition [location node-id]

2. Remove any non-critical data from the primary boot device.

3. configure

4. mirror [location node-id ] primary-device: secondary-device:

5. end
or
commit

6. show mirror [location node-id]

7. mirror verify [location node-id]

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

format secondary-device partition [location 
node-id]
Example:
RP/0/0/CPU0:router# format disk1: partition
 
        
This operation will destroy all data on 
"disk1:" and partition device.
Continue? [confirm]
Y
Device partition disk1: is now formatted 
and is available for use.

Destroys all data on disk1: and partitions the secondary device.

Step 2 

configure

Example:

RP/0/0/CPU0:router# configure

RP/0/0/CPU0:router(config)#

Enters the global configuration mode.

Step 3 

mirror [location node-id] 
primary-device:secondary-device:
Example:
RP/0/0/CPU0:router(config)# mirror location 
0/0/cpu0 disk0: disk1:

Mirrors the content from the primary storage device onto the secondary storage device.

Step 4 

end
or

commit

Example:

RP/0/RP0/CPU0:router(config# end

or

RP/0/RP0/CPU0:router(config)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting(yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Step 5 

show mirror location {all |node-id}
Example:

RP/0/RP0/CPU0:router# show mirror location all

Displays disk mirroring information.

Step 6 

mirror verify [location node-id]
Example:

RP/0/RP0/CPU0:router# mirror verify 0/0/cpu0 disk1:

Verifies disk synchronization for disk mirroring on a specified RP node in a multishelf system.

Cloning a Disk

Like the other disk swapping methods, disk cloning replicates the critical data from the primary boot device onto another storage device (secondary location) within the same RP.

Disk cloning can be used to create duplicates of a seed Cisco IOS XR software disk. You can then move the duplicate disks to the target systems to enable them to boot the Cisco IOS XR operating system.

Disk cloning refers to creating a binary copy of a working Cisco IOS XR software disk onto a target disk using Cisco or third-party utilities. For example, you can replicate a disk using Microsoft Windows, UNIX, or Linux machines equipped with flash disk readers.


Warning If you are migrating to a release earlier than Release 3.8.0 and want to use disk cloning, the target disk must be formatted with the FAT16 file system.

SUMMARY STEPS

1. Install a formatted flash disk on the secondary storage device within the route processor.

2. From an EXEC mode prompt on the Cisco XR 12000 Series Router, enter:

run cp -r source-device-n:/target-device-n:
 
   

3. Remove the disk you seeded.


Note The following example assumes that the procedure is taking place on a Cisco router rather than a third-party router.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

Install a formatted flash disk on the secondary storage device within the RP.

Makes media available on which to make a copy to be used for replication.

Step 2 

From EXEC mode, enter:

run cp -r source-device-n:/target- 
device-n: 
Example:

RP/0/0/CPU0:Router# run cp -r /disk0: /disk1:

Copies the disk residing at the source address to the target destination.

The -r flag refers to recursive. In other words, the copy operation should copy everything, including subdirectories and directories within subdirectories.

When used without the flag, the cp command by default copies just the files explicitly specified.

Step 3 

Remove the disk you seeded.

The disk is now ready for seeding nodes in your network with Cisco IOS XR software.

Swapping a PRP

PRP pre-staging involves preparing the PRP in a staging environment with the correct Cisco IOS XR software release and, optionally, pre-configuring the PRP with the configuration needed by the target. The pre-staged PRP is then shipped to the target production sites, where the migration is performed by removing the Cisco IOS software-configured PRPs and installing the Cisco IOS XR software-configured PRPs in their place.

One advantage of PRP swapping is that it minimizes the downtime of the target router to the time it takes to power down the router, change the hardware, power up the system, and wait for the router to complete the boot process.

PRP swapping also makes sense if your organization is already planning on migrating from a PRP 2-based systems to a PRP 3-based system, because you thereby maximize efficiency by combining these two efforts.

There are two primary means of pre-staging the PRP:

Use the direct migration method to migrate to Cisco IOS XR software on the target PRP in a staging environment.

Prestage a Cisco IOS XR software disk by performing one of the disk replication methods described elsewhere and insert that disk into the target PRP before shipment to the target destination.

SUMMARY STEPS

1. Prestage the target PRPs, using either Turboboot or disk swapping.

2. Ship the PRPs to the target destination.

3. Power down the router.

4. Remove all Cisco IOS software-configured PRPs.

5. Install all the Cisco IOS XR software PRPs in the same slots.

6. Power up the router.

7. Boot Cisco IOS XR software.

8. Boot the line cards.

What to Do If Your Migration Fails

Migrations typically fail due to user error; a careful review of current Release Notes for Cisco IOS XR Software, as well as the topics in this guide, should help you to avoid most of these problems.

This section describes troubleshooting you can perform to assess where you may have gone wrong, as well as how to revert to your previous OS image:

Troubleshooting a Failed Migration: Examples

Reverting to Cisco IOS from Cisco IOS XR Software

Troubleshooting a Failed Migration

The issues described in this section are the most common problems Cisco customers have in past encountered when performing a migration to Cisco IOS XR software.

This section does not provide a complete list of all error messages you might receive during the course of a migration.


Note Symptoms 5, 8, and 9 are seen exclusively during a direct migration.


For more troubleshooting information, see also Troubleshooting a Failed Migration: Examples.

Symptom    1: During a system reload or a cold start of Cisco IOS XR software, the following message appears:

%Error opening slot0:/ (No device available)
 
   

The router may stop the startup process and remain in ROMMON mode.

Possible Cause    Your flash disk may be defective and require replacement.

Recommended Action    Run the check disk utility using the following command:

run chkdosfs -n disk0:
 
   

If the disk has no defects, the following appears:

Filesystem is clean
Example:
Phase 1 - Read and compare FATs
Phase 2 - Check cluster chains
Phase 3 - Check directories
Phase 4 - Check for lost files
368192 kb used, 632336 kb free, 5859 files, 370 directories Filesystem is clean.
RP/0/0/CPU0:PRP161A-BR#

Recommended Action    For details about a possibly defective flash disk and available remedies, see Field Notice FN - 62784 - GSR PRP-1 and PRP-2 at https://www.cisco.com/en/US/ts/fn/620/fn62784.html.

The following table illustrates specific Cisco XR 12000 Series Router products that may have shipped with suspect flash disks between January 2006 and October 2006. The S/N Location (Quadrant) heading refers to the physical location of the serial number decal on the specific product. Quadrant 2 is located on the upper right corner of the card, which is divided into four quadrants. See FN - 62784 for more detail.

S/N Location (Quadrant)
Product ID
Serial Number Range

2

PRP-1

SAD092303JC To SAD104103FG

2

PRP-2

SAD092101SE To SAD111603GY

Symptom    2: During Cisco IOS XR software installation or startup, the following message appears:

Use the `upgrade mbus CLI in admin mode.'

Possible Cause    Your Mbus version is not current.

Recommended Action    For code output illustrating resolution, see the section Upgrading the Mbus Firmware: Example.

Symptom    3: During Cisco IOS XR software installation or startup, the following message appears:

`fabric-downloader is down-rev (V5.6), consult technical support.'

Possible Cause    Your fabric downloader version is not current.

Recommended Action    For code output illustrating resolution, see the section Upgrading the Fabric Downloader: Example.

Symptom    4: After performing Step 22 on page 26, line card status is reported as a ROM response:

Board State is Getting ROM Response (ROM  VGET)
SLOT 1  (RP/LC 1 ): 4 Port ISE Packet Over SONET OC-3c/STM-1 Single Mode/IR LC 
connector
  MAIN: type 83,  800-21485-06 rev A0
        Deviation: 0
        HW config: 0x01    SW key: 00-00-00
  PCA:  73-8090-05 rev A0 ver 2
        Design Release 1.0  S/N SAD1007047M
  MBUS: Embedded Agent
        Test hist: 0x00    RMA#: 00-00-00    RMA hist: 0x00
  DIAG: Test count: 0x00000000    Test results: 0x00000000
  FRU:  Linecard/Module: 4OC3X/POS-IR-LC-B=
  L3 Engine: 3 - ISE OC48 (2.5 Gbps)
  MBUS Agent Software version 1.117 (RAM) (ROM version is 2.0)
  Fabric Downloader version used n/a (ROM version is UNKNOWN)
  Primary clock is CSC 1
  Board State is Getting ROM Response (ROM  VGET)
  Insertion time: 00:00:45 (00:01:27 ago)

Possible Cause    Line card firmware is not at the minimum level to run Cisco IOS XR software.

Recommended Action    Remove any memory that you previously added to the line card. (Refer to the document Cisco 12000 Series Router Memory Replacement Instructions.) Then, perform the line card upgrade and reinstall Cisco IOS XR software using either of the following methods.

Solution   A

1. Put the line cards in another chassis that is running the minimum version of firmware or a later version, and then repeat the upgrade of the firmware by entering:

Router# upgrade all slot slot-number
 
   

2. Reinstall the line card into the original chassis.

Solution   B

1. Remove the line cards from the chassis and restore their physical memory to their premigration level.

2. Restart the router onto Cisco IOS, using the minimum image level recommended or a later level. (See Table 2.)

3. Perform the firmware upgrade of the affected line cards. For more information, see the "Verifying Line Card Firmware" section.

4. Reinstall Cisco IOS XR software, as described in the "Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router" section.

Symptom    5: After you use the TURBOBOOT variable during Cisco IOS XR software installation, the following messages appear in syslog:

Info:     Checking available free space in disk0: 
Router:# May 16 11:30:03.596 : instdir[196]: 
%INSTALL-INSTMGR-3-INSTALL_OPERATION_USER_ERROR : User error occurred during install 
operation 1. See 'show install log 1' for more information. 
Router:# May 16 11:30:03.600 : instdir[1]: 
%INSTALL-INSTMGR-6-INSTALL_OPERATION_FAILED : Install operation 1 failed  
Error:    Required space 184270848 > available space 69402624, try freeing up 
Error: some space in disk0: Install operation 1 failed at 11:30:03 UTC Tue May 16 
2006. 

Possible Cause    Your disk may be full.

Recommended Action    Verify space requirements against the current Release Notes for Cisco IOS XR Software. Follow the procedure in the "Preparing the Target Device" section, then reinstall Cisco IOS XR software.

Symptom    6: During startup of Cisco IOS XR software, a message similar to the following appears:

rommon# boot tftp://192.168.1.2/c12k-mini.vm-3.x.x Self decompressing the image : [OK] 
boot of "tftp c12k-mini.vm-3.x.x 192.168.1.2" using Boothelper 
"bootflash:c12kprp-boot-mz.120-31.S0a" failed error returned: No usable interfaces 
loadprog: error - on file openboot:  cannot load "tftp c12k-mini.vm-3.x.x 192.168.1.2" 

Possible Cause    An outdated version of Cisco IOS Boothelper was used.

Recommended Action    You must upgrade Cisco IOS Boothelper to the minimum level and reattempt Cisco IOS XR migration from the beginning. (For the minimum level, see Release Notes for Cisco IOS XR Software for the current release and perform the procedures in How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software.)

Symptom    7: Each time the router is restarted, the following message appears:

Router# instdir[196]: %INSTALL-PKG_PLAT-7-INVALID_BOOTHELPER_VERSION : Unable to find 
valid GSR boothelper filename 

Possible Cause    You used an outdated version of Cisco IOS Boothelper.

Recommended Action    You must upgrade Cisco IOS Boothelper to the minimum level and reattempt Cisco IOS XR migration from the beginning. (For the minimum level, see Release Notes for Cisco IOS XR Software for the targeted release and perform the procedures in Verifying Cisco IOS Boothelper)

Symptom    8: When Cisco IOS XR software initializes as part of the Cisco IOS XR migration procedure, the following warning message appears:

Router:# Jul  5 21:46:02.905 : easybake 3[166]: 
%INSTALL-TURBOBOOT-4-ROMMON_VARIABLE_NOT_SET : TURBOBOOT rommon variable not set; 
system is membooting.

Possible Cause    You forgot to use the on keyword while setting the TURBOBOOT variable.

Recommended Action    Repeat all the Cisco IOS XR software installation steps, making sure to include the on keyword when you issue the TURBOBOOT command. See the "Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router" section.

Symptom    9: During Cisco IOS XR software installation, a message similar to the following appears:

*** insthelper: Booted with wrong image type. Composite *** has already been used to 
boot dSC at 0/8/CPU0. *** Please boot this node with an MBI image. 

Possible Cause    A) You tried to boot with the primary image rather than the standby image on the standby RP.

Recommended Action    A) Reboot using the correct image for the standby RP.


Note This recommendation assumes that your primary RP installation was initiated correctly. If it was not, you must reinstall starting from Step 7 on page 24.


Possible Cause    B) You failed to bring the standby RP into ROMMON mode before upgrading the primary RP, so the software assumes that the standby RP should now function as the primary RP.

Recommended Action    B) Take both RPs down to the ROMMON level and reinstall Cisco IOS XR software. For information, see the "Installing Cisco IOS XR Software on a Dual-RP Cisco XR 12000 Series Router" section.

Reverting to Cisco IOS from Cisco IOS XR Software

Use this procedure only after you have first reviewed Troubleshooting a Failed Migration and you have verified that your attempted migration was unsuccessful, requiring you to revert back to your previous Cisco IOS software image.


Tip This example assumes that the Cisco IOS image is stored on disk1: If disk1: does not exist, start up from the bootflash: image, format disk0:, and then copy a new Cisco IOS software image onto disk0:. This removes any Cisco IOS XR software previously installed.


SUMMARY STEPS

1. directory target-disk

2. admin

3. config-reg 0x0

4. reload location all

5. unset TURBOBOOT

6. sync

7. reset

8. boot target-disk:Cisco-IOS-image-name

9. upgrade all all force

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

directory target-disk
Example:
RP/0/0/CPU0:Router:# directory disk1:

Locates the Cisco IOS image on disk1:.

Step 2 

admin
Example:
RP/0/0/CPU0:Router:# admin

Switches to administrative mode.

Step 3 

config-reg 0x0
Example:
RP/0/0/CPU0:Router(admin)# config-reg 0x0

Changes the Configuration Register Boot field settings.

Step 4 

reload location all
Example:
RP/0/0/CPU0:Router(admin)# reload location all
 
        
rommon1>#

Reloads all the nodes on the router, and drops into ROMMON mode.

Step 5 

unset TURBOBOOT
Example:
rommon1># unset TURBOBOOT

Clears the router monitor TURBOBOOT variable.

Step 6 

sync
Example:

rommon2># sync

Writes the monitor environment variables to NVRAM.

Step 7 

reset
Example:

rommon3># reset

Resets the router.

Step 8 

boot target-disk:Cisco-IOS-image-name
Example:
rommon4># boot disk1:c12kprp-p-mz.120-32.SY2.bin

Loads the router with the Cisco IOS image.

Step 9 

upgrade all all force
Example:
Router:# upgrade all all force

Returns the line cards to their previous Cisco IOS levels for features such as Mbus agent, RAM and ROM, and fabric downloader.

Migrating from Cisco IOS to Cisco IOS XR Software: Examples

How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software: Examples

How to Perform a Direct Migration: Example

How to Perform a Pre-staged Migration: Example

Troubleshooting a Failed Migration: Examples

How to Audit Your Network to Prepare for Migration to Cisco IOS XR Software: Examples

Verifying Your Cisco IOS Image: Example

Verifying Cisco IOS Boothelper: Example

Verifying Cisco ROM Monitor: Example

Verifying Cisco IOS Firmware: Example

Verifying Line Card Memory: Example

Verifying Your Cisco IOS Image: Example

In the example below, the Cisco IOS image level does not meet the minimum requirements for migration to Cisco IOS XR Software Release 3.8.0.

RP/0/RP0/CPU0:router# show version 
 
   
Cisco Internetwork Operating System Software IOS (tm) GS Software (C12KPRP-BOOT-M), 
Version 12.0(31)S0a, RELEASE SOFTWARE (fc1) 
Technical Support: http://www.cisco.com/techsupport 
Copyright (c) 1986-2005 by cisco Systems, Inc. 
Compiled Fri 10-Jun-05 11:52 by pwade 
Image text-base: 0x00010000, data-base: 0x0095D000 
ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE BOOTLDR: GS Software (C12KPRP-BOOT-M), Version 12.0(31)S0a, RELEASE 
SOFTWARE (fc1) 
MELL_PE_1 uptime is 15 weeks, 1 day, 59 minutes 
Uptime for this control processor is 15 weeks, 1 day, 59 minutes

Verifying Cisco IOS Boothelper: Example

This example shows how to verify the current level of Cisco IOS Boothelper and then upgrade it. In this example, Cisco IOS Boothelper Release 12.0(30)S3, shown in bold, mandates an upgrade.

For the current minimum Cisco IOS Boothelper version, see the Cisco IOS XR Software Release Notes for the targeted release.

Router# dir bootflash:
 
   
1    -rwx  3449752     Tue May22 02:10:02 2008 c12kprp-boot-mz.120-30.S3
 
66322432 bytes total (0 bytes free)
 
   
Router# configure terminal
Router(config)# ip default-gateway 192.168.16.23

Router(config)# interface Ethernet0

Router(config-if)# ip address 192.168.16.1 255.255.255.0

Router(config-if)# no shutdown

Router(config)# exit

Router# copy running-config startup-config

Router# show interface Ethernet0

Router# ping 192.168.16.1

Router# delete bootflash:*
Delete filename [*]? 
[confirm] 
 
   
Router# dir bootflash: 
Directory of bootflash:/ 
 
   
No files in directory 
66322432 bytes total (62872484 bytes free)

Router# squeeze bootflash:

 
   
All deleted files will be removed. Continue? [confirm]
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Router# dir bootflash:
Directory of bootflash:/
 
   
No files in directory
 
   
66322432 bytes total (66322432 bytes free)
Router#
Router# copy tftp: bootflash: Address or name of remote host [192.168.16.1]? 
Source filename [auto/tftpboot-users/c12kprp-boot-mz.120-32.S]? 
Destination filename [c12kprp-boot-mz.120-32.S]? 
Accessing tftp:/192.168.16.1/auto/tftpboot-users/c12kprp-boot-mz.120-32.S3... 
Loading auto/tftpboot-users/c12kprp-boot-mz.120-32.S3 from 192.168.16.1 (via Ethernet0):
 
   
[OK - 3878244 bytes]
 
   
3878244 bytes copied in 31.776 secs (122049 bytes/sec)
 
   
Router# dir bootflash:
Directory of bootflash:/
 
   
    1  -rw-     3878244   Jun 8 2008 18:27:37 +00:00  c12kprp-boot-mz.120-32.S3
66322432 bytes total (62444060 bytes free)

Verifying Cisco ROM Monitor: Example

The following examples shows how to display the current ROM Monitor version on the installed route processor cards and how to upgrade them:

Router# show diags | include SLOT | ROM Monitor

SLOT 0  (RP/LC 0 ): Performance Route Processor

ROM Monitor version 1.17(0.5) <<Requires an upgrade to the current min. version.

SLOT 1  (RP/LC 1 ): Performance Route Processor

ROM Monitor version 1.17(0.5) <<Requires an upgrade to the current min. version.

SLOT 6 (RP/LC 6 ): Modular SPA Interface Card (10G)

ROM Monitor version 17.1

SLOT 16 (CSC 0 ): Clock Scheduler Card(10) OC-768E

SLOT 17 (CSC 1 ): Clock Scheduler Card(10) OC-768E

SLOT 18 (SFC 0 ): Switch Fabric Card(10) OC-768

SLOT 19 (SFC 1 ): Switch Fabric Card(10) OC-768

SLOT 20 (SFC 2 ): Switch Fabric Card(10) OC-768

SLOT 21 (SFC 3 ): Switch Fabric Card(10) OC-768

SLOT 22 (SFC 4 ): Switch Fabric Card(10) OC-768

SLOT 24 (PS A1 ): Alarm Module(10)

SLOT 25 (PS A2 ): Alarm Module(10)

SLOT 29 (BOT FAN ): Enhanced Blower Module(16)

Router# upgrade rom-monitor slot 0 force

Router# upgrade rom-monitor slot 1 force

Verifying Cisco IOS Firmware: Example

The following example illustrates verification of firmware on each line card in the router (the bolded output shows that the version is not up to date and requires upgrade) and the upgrade:

Router# show diags | inc SLOT | MBUS | Fabric Downloader

SLOT 0 (RP/LC 0 ): Performance Route Processor

MBUS: MBUS Agent (1) 73-8048-07 rev A0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 2 (RP/LC 2 ): 4 Port ISE Packet Over SONET OC-3c/STM-1 Multi Mode/SR MTRJ connector

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

Fabric Downloader version used n/a (ROM version is 7.3)

SLOT 3 (RP/LC 3 ): 4 Port ISE Packet Over SONET OC-3c/STM-1 Multi Mode/SR MTRJ connector

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

Fabric Downloader version used n/a (ROM version is 7.3)

SLOT 4 (RP/LC 4 ): 4 Port ISE Gigabit Ethernet

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

Fabric Downloader version used n/a (ROM version is 7.3)

SLOT 5 (RP/LC 5 ): 4 Port ISE Packet Over SONET OC-12c/STM-4 Multi Mode/SR SC connector

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

Fabric Downloader version used n/a (ROM version is 7.3)

SLOT 16 (CSC 0 ): Clock Scheduler Card(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 17 (CSC 1 ): Clock Scheduler Card(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 18 (SFC 0 ): Switch Fabric Card(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 19 (SFC 1 ): Switch Fabric Card(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 20 (SFC 2 ): Switch Fabric Card(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

SLOT 26 (PS B1 ): AC Power Supply(8)

MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0

MBUS Agent Software version 2.51 (RAM) (ROM version is 3.50)

Router# show version

Cisco Internetwork Operating System Software IOS (tm) GS Software (C12KPRP-P-M), Version 
12.0(32)S, RELEASE SOFTWARE (fc2) 
Technical Support: http://www.cisco.com/techsupport 
Copyright (c) 1986-2006 by cisco Systems, Inc. 
Compiled Wed 18-Oct-06 16:27 by leccese 
Image text-base: 0x00010000, data-base: 0x050B4000  
 
   
ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE BOOTLDR: GS Software (C12KPRP-BOOT-M), Version 12.0(31)S0a, RELEASE 
SOFTWARE (fc1)   
 
   
GSR-R3 uptime is 13 weeks, 4 days, 17 hours, 45 minutes Uptime for this control processor 
is 13 weeks, 4 days, 17 hours, 45 minutes System returned to ROM by reload at 01:19:07 UTC 
Sun Apr 1 2008 System image file is 
"tftp://223.255.254.254/users/srwa/gsr/c12kprp-p-mz.120-32.S.bin"  cisco 12410/PRP 
(MPC7457) processor (revision 0x00) with 2097152K bytes of memory. MPC7457 CPU at 1263Mhz, 
Rev 1.1, 512KB L2, 2048KB L3 Cache Last reset from sw reset Channelized E1, Version 1.0.            
2 Route Processor Cards 
2 Clock Scheduler Cards 
5 Switch Fabric Cards 
4 T1/E1 BITS controllers 
1 OC48 POS controller (1 POS). 
2 ISE 10G SPA Interface Cards (12000-SIP-600) 
3 Ethernet/IEEE 802.3 interface(s) 
5 GigabitEthernet/IEEE 802.3 interface(s) 
1 10GigabitEthernet/IEEE 802.3 interface(s) 
3 Packet over SONET network interface(s) 
4 SDCC network interface(s) 2043K bytes of non-volatile configuration memory.  
1000944K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes). 
250880K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes). 
65536K bytes of Flash internal SIMM (Sector size 256K). 
Configuration register is 0x0  
WARNING: Unknown MBUS agent controller type, slot 16 Contact your technical support 
representative. 

Router# upgrade all all

Verifying Line Card Memory: Example

The following example shows the verification of line-card memory in preparation for the installation of Cisco IOS XR software. Slots 0 and 1 in the following example show the required 2 GB of route memory in the primary route processor (PRP) card and 2 GB of memory in the shared port adapter (SPA) interface processor card. However, Slot 2 lacks the required memory and requires a memory upgrade.

Router# show diags | inc SLOT | Memory
 
   
SLOT 0 (RP/LC 0 ): Performance Route Processor
        Route Memory: MEM-PRP/LC-2048=
SLOT 1 (RP/LC 1 ): Performance Route Processor
        Route Memory: MEM-PRP/LC-2048=
SLOT 2  (RP/LC 2 ): 4 Port ISE Packet Over SONET OC-3c/STM-1 Multi Mode/SR MTRJ connector
Processor Memory: MEM-LC-ISE-512=
Packet Memory: MEM-LC1-PKT-512=(Non-Replaceable) <<Requires upgrade.
...
SLOT 6  (RP/LC 6 ): Modular SPA Interface Card (10G)
        Processor Memory: MEM-LC5-2048=(Non-Replaceable)
        Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)
  Processor Memory size: 2147483648 bytes
  TX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
  RX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
SLOT 16 (CSC 0   ): Clock Scheduler Card(10) OC-768E
SLOT 17 (CSC 1   ): Clock Scheduler Card(10) OC-768E
SLOT 18 (SFC 0   ): Switch Fabric Card(10) OC-768
SLOT 19 (SFC 1   ): Switch Fabric Card(10) OC-768
SLOT 20 (SFC 2   ): Switch Fabric Card(10) OC-768
SLOT 21 (SFC 3   ): Switch Fabric Card(10) OC-768
SLOT 22 (SFC 4   ): Switch Fabric Card(10) OC-768
SLOT 24 (PS A1   ): Alarm Module(10)
SLOT 25 (PS A2   ): Alarm Module(10)
SLOT 29 (BOT FAN ): Enhanced Blower Module(16)

How to Perform a Direct Migration: Example

Installing Cisco IOS XR Software on the Primary RP: Example

Installing Cisco IOS XR Software on a Standby RP: Example

Installing Cisco IOS XR Software on the Primary RP: Example

The following example illustrates installing Cisco IOS XR software on the primary RP:

Router# config terminal
 
   
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# config-register 0x0
Router(config)# end
Router# write mem
 
   
Building configuration...
[OK]
 
   
Router# reload
 
   
Proceed with reload? [confirm]
 
   
System Bootstrap, Version 12.0(20051020:160303) [sjabbar-CSCsa64979_4 1.17dev(0.5)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2005 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 1024M found 
MPC7457 platform with 2097152 Kbytes of main memory
 
   
rommon 1 > unset BOOT
rommon 2 > TURBOBOOT=on,disk0,format
rommon 3 > sync
rommon 4 > reset
rommon 4 > set
 
   
System Bootstrap, Version 12.0(20051020:160303) [sjabbar-CSCsa64979_4 1.17dev(0.5)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2005 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 512M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
rommon 5> boot tftp://223.255.254.254/auto/tftpboot-users/c12k-mini.vm-3.8.0
 
   
Self decompressing the image : BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB [OK]
 
   
Loading auto/tftpboot-users/c12k-mini.vm-3.8.0 from 223.255.254.254 (via Ethernet0): 
 
   
...
[OK - 144214796 bytes]
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2 
 
   
              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 PRP, Version 3.8.0
Copyright (c) 2009 by Cisco Systems, Inc.
RP/0/0/CPU0:May 19 15:47:08.224: syslogd_helper: [87]: dsc_event_handler: Got SysMgr dSC 
event : 1
TURBOBOOT: Turboboot process started
TURBOBOOT: Checking size of device disk0:
TURBOBOOT:    OK
RP/0/0/CPU0:Jan  1 00:00:25.636 : mbus-prp[63]: mbus-prp: slot 0: mbus rom agent is 
down-rev (V3.47), suggest upgrade to current (V4.4). Use the "upgrade mbus" CLI in admin 
mode. 
RP/0/0/CPU0:May 19 15:46:18.719 : nvram[69]: %MEDIA-NVRAM-6-UPGRADING : nvram upgrade: 
upgrading successful 
RP/0/0/CPU0:May 19 15:46:18.734 : nvram[69]: %MEDIA-NVRAM-6-UPGRADING : nvram upgrade: 
backup all files under nvram:/ if downgrade to 3.5 or under 
RP/0/0/CPU0:May 19 15:46:19.711 : dumper[56]:  No HDD Controller found by process dumper 
RP/0/0/CPU0:May 19 15:46:20.584 : nvram[69]: %MEDIA-NVRAM-4-BADFILES : NVRAM File 
Corrupted (spm_db). Some of them May be Lost 
RP/0/0/CPU0:May 19 15:46:20.625 : nvram[69]: %MEDIA-NVRAM-4-BADFILES : NVRAM File 
Corrupted (sam_db). Some of them May be Lost 
RP/0/0/CPU0:May 19 15:46:53.056 : sysmgr[88]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
RP/0/0/CPU0:May 19 15:47:01.132 : dsc[170]: DSC Election entry delay time for this RP is 4 
seconds 
RP/0/0/CPU0:May 19 15:47:08.148 : dsc[170]: %PLATFORM-DSC-6-ERR_I_AM_DSC : Setting myself 
as DSC 
RP/0/0/CPU0:May 19 15:47:10.343 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 17: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.345 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 18: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.346 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 19: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.346 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 20: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.346 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 28: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.391 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 5: mbus rom agent is down-rev (V3.51), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:10.867 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 4: mbus rom agent is down-rev (V4.2), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:11.624 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 24: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:11.625 : mbus-prp[63]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : 
slot 25: mbus rom agent is down-rev (V3.47), suggest upgrade to current (V4.4). Use the 
"upgrade mbus" CLI in admin mode. 
RP/0/0/CPU0:May 19 15:47:27.797 : cfgmgr-rp[138]: %MGBL-CONFIG-4-VERSION : Version of 
existing commit database detected to be incompatible with the installed software. 
Configuration Manager will remove previous rollback points and reinitialize the commit 
database. Configuration will be restored from an alternate source and may take longer than 
usual on this boot. 
RP/0/0/CPU0:May 19 15:47:21.398 : mbus_flash_driver[269]: No file system detected on 
(null) -- Please format 
RP/0/0/CPU0:May 19 15:47:34.810 : parser[315]: %MGBL-PARSER-3-UNRESOLVED_LINKPOINT : 
Failed to resolve linkpoint 'show bundle' specified in chainname 'show_bundle_trace' in 
'/pkg/parser/bundlemgr_cmds.parser' file. 
RP/0/0/CPU0:May 19 15:47:51.351 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : Waiting for 
startup config to be applied before booting LCs 
RP/0/0/CPU0:May 19 15:47:52.421 : sysldr[372]: %PLATFORM-SYSLDR-4-SPA_WARNING : slot4: 
Could not discover inserted SPA types, no response received to our mbus request 
 
   
 
   
Primary Clock is CSC_1
Fabric Clock is Non Redundant
Bandwidth Mode : Full Bandwidth
 
   
RP/0/0/CPU0:May 19 15:47:57.428 : sysldr[372]: %PLATFORM-SYSLDR-5-OIRIN : OIR: Node 0/4/0 
inserted  
RP/0/0/CPU0:May 19 15:47:59.168 : sysldr[372]: %PLATFORM-POWERMGR-6-INFO : PEMs are in 
Non-Redundancy Mode now 
RP/0/0/CPU0:May 19 15:47:59.939 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/0/CPU0, state: IOS XR RUN  
RP/0/0/CPU0:May 19 15:48:02.131 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 15:48:07.692 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 15:48:08.555 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : Startup config 
applied, resuming work 
RP/0/0/CPU0:May 19 15:48:08.568 : fctl[194]: %PLATFORM-FABRIC_CTRL-3-UNKNOWN_MSG : Unknown 
msg from slot 0 with msg type 0x12 
RP/0/0/CPU0:May 19 15:48:10.623 : psarb[327]: %PLATFORM-PSARB-6-GO_ACTIVE : Card is going 
active. 
TURBOBOOT: C
 
   
ios con0/0/CPU0 is now available
 
   
Press RETURN to get started.
 
   
leaning disk0:
RP/0/0/CPU0:May 19 15:48:23.794 : ifmgr[205]: %PKT_INFRA-IFMGR-3-RULES_DUPLICATE_ID : 
Error: Duplicate ID 15 found in rules file /pkg/rules/plim_iox_4p_ge.intf 
RP/0/0/CPU0:May 19 15:49:37.295 : netio[298]: %ROUTING-FIB-2-INIT : FIB initialization 
failure: fwd-init:li-dll init failed No such process 
RP/0/0/CPU0:May 19 15:49:37.301 : netio[298]: %PKT_INFRA-NETIO-3-ERR_INIT : 
ipv4_proto_init_v2 : Failed to initialize ipv4 proto for IPv4: FIB fwding init failed with 
error (No such process) 
RP/0/0/CPU0:May 19 15:49:58.081 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/0/CPU0 changed to ACTVRP   in state default  
RP/0/0/CPU0:May 19 15:50:01.456 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/0/CPU0 changed to XR  PREP in state default  
RP/0/0/CPU0:May 19 15:50:04.427 : sysmgr[88]: %OS-SYSMGR-4-MANDATORY_REBOOT_OVERRIDE : 
mandatory reboot option overridden by request 
TURBOBOOT: Cleaning disk0: complete
Install operation 1 '(admin) install copy-package mem: to disk0:' started by
RP/0/0/CPU0:May 19 15:50:45.300 : instdir[208]: 
%INSTALL-INSTMGR-6-INSTALL_OPERATION_STARTED : Install operation 1 '(admin) install 
copy-package mem: to disk0:' started by user '(Unknown)' 
user '(Unknown)' via CLI at 15:50:45 UTC Tue May 19 2009.
Info:     Checking available free space in disk0:
Info:     Copying installed files from mem: to disk0:
Info:      Copying component 'boot-mbi-prp-drp' size > 14 MB.
Info:      Copying component 'c12000-boot-mbiprp.4k' size > 11 MB.
Info:      Copying component 'boot-mbi-prp' size > 14 MB.
Info:      Copying component 'installmgr' size > 5 MB.
Info:      Copying component 'config-cfgmgr' size > 1 MB.
Info:      Copying component 'drivers-media-eth' size > 1 MB.
Info:      Copying component 'ha-lrd.4k' size > 1 MB.
Info:      Copying component 'ha-lrd' size > 1 MB.
Info:      Copying component 'ifmgr.4k' size > 1 MB.
Info:      Copying component 'ifmgr' size > 2 MB.
Info:      Copying component 'infra-distrib.4k' size > 1 MB.
Info:      Copying component 'infra-distrib' size > 1 MB.
Info:      Copying component 'infra-ital' size > 1 MB.
Info:      Copying component 'infra-license' size > 2 MB.
Info:      Copying component 'policymgr' size > 1 MB.
Info:      Copying component 'ip-iarm' size > 1 MB.
Info:      Copying component 'ip-rib' size > 1 MB.
Info:      Copying component 'ip-tcp' size > 1 MB.
Info:      Copying component 'ipv4-dhcpd' size > 1 MB.
Info:      Copying component 'l2-eth-infra.4k' size > 1 MB.
Info:      Copying component 'l2-eth-infra' size > 1 MB.
Info:      Copying component 'man-editor-jed' size > 1 MB.
Info:      Copying component 'parser' size > 1 MB.
Info:      Copying component 'perl-56' size > 1 MB.
RP/0/0/CPU0:May 19 15:56:07.182 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
Info:      Copying component 'service-infra-svii' size > 1 MB.
Info:      Copying component 'snmp-agent' size > 1 MB.
Info:      Copying component 'sysdb.4k' size > 1 MB.
Info:      Copying component 'sysdb' size > 2 MB.
Info:      Copying component 'sysmgr.4k' size > 1 MB.
Info:      Copying component 'sysmgr' size > 1 MB.
Info:      Copying component 'xml-parser' size > 2 MB.
Info:      Copying component 'drivers-vpa-infra.4k' size > 3 MB.
Info:      Copying component 'c12000-ucode-rp' size > 2 MB.
Info:      Copying component 'fib-common.4k' size > 1 MB.
Info:      Copying component 'fib-common' size > 3 MB.
Info:      Copying component 'l2vpn.4k' size > 1 MB.
Info:      Copying component 'l2vpn' size > 3 MB.
Info:      Copying component 'CompID-0x0C25.4k' size > 2 MB.
Info:      Copying component 'c12000-cx27470.4k' size > 1 MB.
Info:      Copying component 'CompID-0x0CE3.4k' size > 1 MB.
Info:      Copying component 'c12000-l2vpn.4k' size > 1 MB.
Info:      Copying component 'c12000-lc-qos-ea.4k' size > 1 MB.
Info:      Copying component 'c12k-def-images.4k' size > 3 MB.
Info:      Copying component 'c12k-vpa-ceop.4k' size > 1 MB.
Info:      Copying component 'CompID-0x0ACA.4k' size > 1 MB.
Info:      Copying component 'clns-isis' size > 3 MB.
Info:      Copying component 'eigrp' size > 1 MB.
Info:      Copying component 'ipv4-bgp' size > 7 MB.
Info:      Copying component 'ipv4-ospf' size > 3 MB.
Info:      Copying component 'ipv6-ospfv3' size > 1 MB.
Info:      
Info:     Packages have been copied to disk0:. Removing this device could be
Info:     disruptive to the system.
Info:      
Info:     New boot image is disk0:c12k-os-mbi-3.8.0/mbiprp-rp.vm
Info:     The newly copied package(s) will be activated upon reload for the
Info:     following card types:
Info:     RP
Info:     RP-PRP3
Info:     DRP
Info:     DRPSC
Info:     OC3-POS-4
Info:     OC12-POS
Info:     GE-3
Info:     OC12-POS-4
RP/0/0/CPU0:May 19 16:00:54.882 : instdir[208]: 
%INSTALL-INSTMGR-6-INSTALL_OPERATION_COMPLETED_SUCCESSFULLY : Install operation 1 
completed successfully 
Info:     OC48-POS
Info:     E3-OC48-POS
Info:     E3-OC12-POS-4
Info:     E3-OC3-POS-16
Info:     E3-OC48-CH
Info:     E3-OC12-CH-4
Info:     E3-OC3-POS-8
Info:     E3-OC3-POS-4
Info:     E3-GE-4
Info:     E5-CEC
Info:     SE-SEC
Info:     E3-OC3-ATM-4
Info:     E3-OC12-ATM-4
Info:     E5-CEC-v2
Info:     E3-OC12-CH-1
Info:     Reload then run this boot image to activate copied packages.
Info:     Package copy operation is complete.
Install operation 1 completed successfully at 16:00:54 UTC Tue May 19 2009.
TURBOBOOT: All node preparations complete:
Node 0/0/CPU0 successfully completed the preparation.
 
   
TURBOBOOT: Resetting TURBOBOOT rommon variable to (TURBOBOOT=).
TURBOBOOT: Setting config-register to autoboot the router and  disable send break.
TURBOBOOT: Turboboot completed successfully: the router will now reload from disk
 
   
 
   
TURBOBOOT: *** RESETTING IN 30 SECONDS ***
 
   
RP/0/0/CPU0:May 19 16:01:03.667 : sysldr[372]: %PLATFORM-SYSLDR-5-RESTART_REQ : Accepted 
restart request for slot 1. Reload initiated by easybake3 (slot=0,pid=102490,tid=1) 
RP/0/0/CPU0:May 19 16:01:03.667 : sysldr[372]: %PLATFORM-SYSLDR-5-RESTART_REQ : Accepted 
restart request for slot 4. Reload initiated by easybake3 (slot=0,pid=102490,tid=1) 
RP/0/0/CPU0:May 19 16:01:03.667 : sysldr[372]: %PLATFORM-SYSLDR-5-RESTART_REQ : Accepted 
restart request for slot 5. Reload initiated by easybake3 (slot=0,pid=102490,tid=1) 
RP/0/0/CPU0:May 19 16:01:03.826 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 16:01:03.957 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 16:01:03.967 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 16:01:03.991 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 16:01:13.108 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
Disconnect slot 0 on a 124x6 chassis
Time when entering reboot: 2009-05-19 16:01:44.691
Time when entering KD:     2009-05-19 16:01:46.570
cause_code=0x04000042, Cause: Turboboot completed successfully                                       
Process: easybake3                                                              
 
   
 check_nvraw_format Invalid TLV found - id 0 at offset 0x0?
System Bootstrap, Version 12.0(20051020:160303) [sjabbar-CSCsa64979_4 1.17dev(0.5)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2005 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 512M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
####################################################################
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2 
              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 PRP, Version 3.8.0
Copyright (c) 2009 by Cisco Systems, Inc.
RP/0/0/CPU0:May 19 16:03:49.820: syslogd_helper: [87]: dsc_event_handler: Got SysMgr dSC 
event : 1
RP/0/0/CPU0:May 19 16:02:41.307 : dumper[56]:  No HDD Controller found by process dumper 
RP/0/0/CPU0:May 19 16:03:27.584 : sysmgr[88]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
RP/0/0/CPU0:May 19 16:03:49.608 : dsc[170]: %PLATFORM-DSC-6-ERR_I_AM_DSC : Setting myself 
as DSC 
RP/0/0/CPU0:May 19 16:03:42.592 : dsc[170]: DSC Election entry delay time for this RP is 4 
seconds 
RP/0/0/CPU0:May 19 16:04:35.679 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : Waiting for 
startup config to be applied before booting LCs 
RP/0/0/CPU0:May 19 16:04:37.902 : sysldr[372]: %PLATFORM-SYSLDR-4-SPA_WARNING : slot4: 
Could not discover inserted SPA types, no response received to our mbus request 
 
   
 
   
Primary Clock is CSC_1
Fabric Clock is Non Redundant
Bandwidth Mode : Full Bandwidth
 
   
RP/0/0/CPU0:May 19 16:04:42.922 : sysldr[372]: %PLATFORM-SYSLDR-5-OIRIN : OIR: Node 0/4/0 
inserted  
RP/0/0/CPU0:May 19 16:04:44.777 : sysldr[372]: %PLATFORM-POWERMGR-6-INFO : PEMs are in 
Non-Redundancy Mode now 
RP/0/0/CPU0:May 19 16:04:55.398 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/0/CPU0, state: IOS XR RUN  
RP/0/0/CPU0:May 19 16:05:16.495 : parser[315]: %MGBL-PARSER-3-UNRESOLVED_LINKPOINT : 
Failed to resolve linkpoint 'show bundle' specified in chainname 'show_bundle_trace' in 
'/pkg/parser/bundlemgr_cmds.parser' file. 
RP/0/0/CPU0:May 19 16:05:21.147 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : Startup config 
applied, resuming work 
RP/0/0/CPU0:May 19 16:05:21.169 : fctl[194]: %PLATFORM-FABRIC_CTRL-3-UNKNOWN_MSG : Unknown 
msg from slot 0 with msg type 0x12 
 
   
 
   
ios con0/0/CPU0 is now available
 
   
 
   
Press RETURN to get started.
 
   
RP/0/0/CPU0:May 19 16:05:23.944 : psarb[327]: %PLATFORM-PSARB-6-GO_ACTIVE : Card is going 
active. 
RP/0/0/CPU0:May 19 16:05:27.237 : invmgr[211]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 
0/5/CPU0 inserted  
RP/0/0/CPU0:May 19 16:05:32.381 : invmgr[211]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 
0/1/CPU0 inserted  
RP/0/0/CPU0:May 19 16:05:37.319 : invmgr[211]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 
0/4/CPU0 inserted  
RP/0/0/CPU0:May 19 16:05:40.266 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 16:05:40.292 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 16:05:43.896 : invmgr[211]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 0/4/0 
inserted  
RP/0/0/CPU0:May 19 16:05:44.104 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 16:05:46.629 : ifmgr[205]: %PKT_INFRA-IFMGR-3-RULES_DUPLICATE_ID : 
Error: Duplicate ID 15 found in rules file /pkg/rules/plim_iox_4p_ge.intf 
RP/0/0/CPU0:May 19 16:06:04.725 : cfgmgr-rp[138]: %MGBL-CONFIG-4-VERSION : Version of 
existing commit database detected to be incompatible with the installed software. 
Configuration Manager will remove previous rollback points and reinitialize the commit 
database. Configuration will be restored from an alternate source and may take longer than 
usual on this boot. 
RP/0/0/CPU0:May 19 16:06:47.151 : netio[298]: %ROUTING-FIB-2-INIT : FIB initialization 
failure: fwd-init:li-dll init failed No such process 
RP/0/0/CPU0:May 19 16:06:47.156 : netio[298]: %PKT_INFRA-NETIO-3-ERR_INIT : 
ipv4_proto_init_v2 : Failed to initialize ipv4 proto for IPv4: FIB fwding init failed with 
error (No such process) 
RP/0/0/CPU0:May 19 16:06:51.796 : netio[298]: %ROUTING-FIB-2-INIT : FIB initialization 
failure: fwd-init:li-dll init failed No such process 
RP/0/0/CPU0:May 19 16:07:25.674 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/0/CPU0 changed to ACTVRP   in state default  
RP/0/0/CPU0:May 19 09:08:56.119 : dumper[56]:  No HDD Controller found by process dumper 
RP/0/0/CPU0:May 19 09:09:02.618 : placed[320]: %OS-PLACED_PLACE-6-REOP_START : 
Re-optimization of the placement requested. You will be notified on completion 
RP/0/0/CPU0:May 19 09:09:02.629 : placed[320]: %OS-PLACED_PLACE-6-REOP_COMPLETE : 
Re-optimization of the placement complete. Use 'show placement' to view the new placement 
RP/0/0/CPU0:May 19 09:09:04.384 : ifmgr[205]: %PKT_INFRA-LINK-5-CHANGED : Interface 
MgmtEth0/0/CPU0/1, changed state to Administratively Down 
RP/0/0/CPU0:May 19 09:09:04.402 : ifmgr[205]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/0/CPU0/0, changed state to Down 
RP/0/0/CPU0:May 19 09:09:04.404 : ifmgr[205]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/0/CPU0/0, changed state to Down 
RP/0/0/CPU0:May 19 09:09:04.418 : cfgmgr-rp[138]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/0/0' has been restored. 
RP/0/0/CPU0:May 19 09:09:04.561 : ifmgr[205]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/0/CPU0/0, changed state to Up 
RP/0/0/CPU0:May 19 09:09:04.578 : ifmgr[205]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/0/CPU0/0, changed state to Up 
RP/0/0/CPU0:May 19 09:12:04.879 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:12:04.926 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:12:28.998 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-161204.nocksum.dsc 
RP/0/0/CPU0:May 19 09:12:43.383 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:12:56.869 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:13:02.246 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 09:13:02.297 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 09:13:02.361 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 09:12:09.924 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 16:12:09.907 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 09:12:58.020 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:May 19 09:13:17.395 : mbus_flash_driver[182]: No file system detected on 
(null) -- Please format 
RP/0/0/CPU0:May 19 09:13:24.772 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
LC/0/5/CPU0:May 19 09:14:22.096 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 796c9e88 796ce0f0 7826e31c
RP/0/0/CPU0:May 19 09:14:22.170 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 09:14:22.208 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 09:14:22.415 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 09:14:22.650 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:14:26.173 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-161422.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 09:14:35.662 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-161422.05.Z file (33737 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 09:14:52.705 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:14:52.755 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:15:20.819 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-161452.nocksum.dsc 
RP/0/0/CPU0:May 19 09:15:35.207 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:15:48.659 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:17:43.955 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:17:44.012 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:18:11.012 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-161743.nocksum.dsc 
RP/0/0/CPU0:May 19 09:18:25.385 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:18:38.867 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:20:33.591 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:20:33.666 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:20:59.639 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-162033.nocksum.dsc 
RP/0/0/CPU0:May 19 09:21:14.020 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:21:27.496 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:21:41.268 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:23:22.552 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:23:22.606 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:23:42.121 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-161422.05.Z file (5360885 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 09:23:48.600 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-162322.nocksum.dsc 
RP/0/0/CPU0:May 19 09:24:00.526 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:24:03.035 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:24:16.484 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V3.9), suggest upgrade to (V6.1), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:26:25.587 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:26:25.637 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
RP/0/0/CPU0:May 19 09:26:28.800 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 09:26:28.850 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 09:26:28.928 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 09:25:30.090 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 16:25:30.073 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 09:26:24.556 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
RP/0/0/CPU0:May 19 09:26:47.606 : sysldr[372]: %PLATFORM-SYSLDR-6-INFO : slot=4: dSC diag 
info in /disk0:/diag/slr_diag_04.20090519-162625.nocksum.dsc 
RP/0/0/CPU0:May 19 09:26:56.829 : sysldr[372]: %PLATFORM-SYSLDR-3-MANY_RESTARTS : slot 4: 
too many reload attempts - stopping 
RP/0/0/CPU0:May 19 09:27:01.135 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/4/0, state: UNKNOWN  
LC/0/5/CPU0:May 19 09:27:44.744 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 7969de88 796a20f0 7826e31c
RP/0/0/CPU0:May 19 09:27:44.795 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 09:27:44.813 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 09:27:45.005 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 09:27:45.010 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:27:48.750 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-162744.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 09:27:58.087 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-162744.05.Z file (32292 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 09:29:57.776 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:34:59.943 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-162744.05.Z file (5381427 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 09:35:18.350 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:37:31.234 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 09:37:31.270 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 09:37:31.296 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 09:36:40.200 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 16:36:40.183 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 09:37:26.821 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
RP/0/0/CPU0:May 19 09:38:12.524 : envmon_periodic[185]: %PLATFORM-ENVMON-2-VOLTAGE : Card 
3.3v supply(slot 1) voltage has reached MAJOR level at 156 mV 
RP/0/0/CPU0:May 19 09:38:12.546 : envmon_periodic[185]: %PLATFORM-ENVMON-2-ENV_CONDITION : 
An environmental condition on slot 1 exists 
RP/0/0/CPU0:May 19 09:38:13.491 : envmon_periodic[185]: %PLATFORM-ENVMON-2-VOLTAGE : Card 
5v supply(slot 1) voltage has reached MAJOR level at 40 mV 
RP/0/0/CPU0:May 19 09:38:14.239 : envmon_periodic[185]: 
%PLATFORM-ENVMON-2-ENV_SLOT_FORCE_CLEAR : The environmental condition on slot 1 has 
cleared because the slot is no longer monitorable 
RP/0/0/CPU0:May 19 09:38:14.287 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
LC/0/5/CPU0:May 19 09:38:46.631 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 7967ce88 796810f0 7826e31c
RP/0/0/CPU0:May 19 09:38:46.730 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 09:38:46.774 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 09:38:46.931 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 09:38:46.942 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:38:50.683 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-163846.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 09:39:00.030 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-163846.05.Z file (32322 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 09:46:01.938 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-163846.05.Z file (5365795 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 09:46:20.338 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:48:33.542 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 09:48:33.575 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 09:48:33.602 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 09:47:40.280 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 16:47:40.263 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 09:48:29.218 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:May 19 09:49:47.981 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 7966de88 796720f0 7826e31c
RP/0/0/CPU0:May 19 09:49:48.058 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 09:49:48.098 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 09:49:48.263 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 09:49:48.271 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 09:49:52.163 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-164948.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 09:50:01.484 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-164948.05.Z file (32228 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 09:56:58.451 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-164948.05.Z file (5319194 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 09:57:16.861 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 09:59:29.469 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 09:59:29.502 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 09:59:29.531 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 09:59:24.992 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:May 19 10:00:44.615 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 7966ee88 796730f0 7826e31c
RP/0/0/CPU0:May 19 10:00:44.668 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 10:00:44.706 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 10:00:44.871 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 10:00:44.876 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 10:00:48.705 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-170044.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 10:00:58.059 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-170044.05.Z file (32366 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 10:07:57.306 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-170044.05.Z file (5343842 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 10:08:15.714 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 10:10:28.499 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 10:10:28.533 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 10:10:28.560 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 10:09:30.454 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 17:09:30.437 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 10:10:23.932 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:May 19 10:11:42.702 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 79681e88 796860f0 7826e31c
RP/0/0/CPU0:May 19 10:11:42.778 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 10:11:42.820 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 10:11:42.979 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 10:11:42.989 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 10:11:47.541 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-171142.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 10:11:56.896 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-171142.05.Z file (32361 bytes) received from 
slot 5. 
RP/0/0/CPU0:May 19 10:14:37.019 : wdsysmon[416]: %HA-HA_WD-4-DISK_ALARM : A monitored 
device alarm set by  /disk1: 
RP/0/0/CPU0:May 19 10:14:37.020 : wdsysmon[416]: %HA-HA_WD-4-DISK_WARN : A monitored 
device /disk1: is above 80% utilization. Current utilization = 80. Please remove unwanted 
user files and configuration rollback points. 
RP/0/0/CPU0:May 19 10:18:54.251 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/kernel_core.by.fault_mgr.20090519-171142.05.Z file (5336208 
bytes) received from slot 5. 
RP/0/0/CPU0:May 19 10:19:12.659 : sysldr[372]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 5: 
fabric-downloader is down-rev (V7.1), suggest upgrade to (V8.0), use "upgrade 
fabric-downloader" CLI in admin mode 
RP/0/0/CPU0:May 19 10:21:25.708 : sysldr[372]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/0/CPU0:May 19 10:21:25.741 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/0/CPU0:May 19 10:21:25.771 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
LC/0/5/CPU0:May 19 10:20:30.556 : timesync_client[82]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 17:20:30.539 UTC Tue May 19 
2009 
LC/0/5/CPU0:May 19 10:21:21.350 : sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:May 19 10:22:39.609 : pl_e48_pos_1p_oc48[220]: %L2-gulf-3-FATAL_ERROR : Fatal 
error: ASIC GULF: Clock failed in RxTB domain: severity: 3  : pkg/bin/pl_e48_pos_1p_oc48 : 
(PID=86112) :  -Traceback= 7967ce88 796810f0 7826e31c
RP/0/0/CPU0:May 19 10:22:39.705 : gsr_prp_pm[60]: %PLATFORM-FAULT-2-LC_RESET : Reset LC 5: 
Reason - PLIM 
RP/0/0/CPU0:May 19 10:22:39.752 : sysldr[372]: %PLATFORM-SYSLDR-6-CARD_KDUMPER : Card 
ungraceful reboot detected in slot 5. 
RP/0/0/CPU0:May 19 10:22:39.925 : invmgr[211]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:May 19 10:22:39.933 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:May 19 10:22:44.529 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/crashinfo.by.fault_mgr.20090519-172239.05 file (46681 bytes) 
received from slot 5. 
RP/0/0/CPU0:May 19 10:22:53.907 : kd_mbus_server[250]: %OS-KD_MBUS-6-KDUMPER_FILE_INFO : 
Successfully wrote disk1:/pcds_data.20090519-172239.05.Z file (32469 bytes) received from 
slot 5. 
 
   
 
   
         --- Administrative User Dialog --- 
  Enter root-system username: lab 
  Enter secret: 
  Enter secret again: 
 
   
User Access Verification 
Username: 
Username: lab 
Password: 
 
   
RP/0/0/CPU0:Router# 
 
   
RP/0/0/CPU0:Router# show platform 
Node            Type            PLIM            State           Config State 
----------------------------------------------------------------------------- 
0/0/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON 
0/1/CPU0        PRP(Standby)    N/A             IOS XR RUN      PWR,NSHUT,MON 
0/4/CPU0        L3LC Eng 5      Jacket Card     IOS XR RUN      PWR,NSHUT,MON 
0/4/0           SPA             SPA-5X1GE       READY           PWR,NSHUT 
0/5/CPU0        L3LC Eng 3      OC48-POS        IOS XR RUN      PWR,NSHUT,MON

Installing Cisco IOS XR Software on a Standby RP: Example

The following example illustrates installing Cisco IOS XR software on the standby RP:

rommon 1 > unset BOOT
rommon 2 > unset TURBOBOOT
rommon 3 > sync
rommon 4 > reset
 
   
System Bootstrap, Version 12.0(20051020:160303) [sjabbar-CSCsa64979_4 1.17dev(0.5)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2005 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 512M found 
MPC7450 platform with 1572864 Kbytes of main memory
 
   
rommon 5 > boot tftp://223.255.254.254/auto/tftpboot-users/mbiprp-rp.vm-3.8.0
 
   
Self decompressing the image : BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB [OK]
 
   
Loading auto/tftpboot-users/mbiprp-rp.vm-3.8.0 from 223.255.254.254 (via Ethernet0): 
 
   
...
 
   
[OK - 9974432 bytes]
++++ Enabling L3 cache, flags = 0x50a38300 ..., old L3CR = 0xdca38340  done, new L3CR = 
0xdca38300 
 L2CR = 0xc0000000, MSSCR0 = 0x01188003 
??###########################################
System page at phys:00023000 user:00023000 kern:00023000
Starting next program at v0026d6cc
mbus-prp: slot 1: mbus rom agent is down-rev (V3.48), suggest upgrade to current (V3.53). 
Use the "upgrade mbus" CLI in admin mode.
              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 PRP, Version 3.8.0
Copyright (c) 2008 by Cisco Systems, Inc.
dumper_config: No HDD Controller found
Install (Node Preparation): Install device root from dSC is /disk0/
Install (Node Preparation): Trying device disk0:
Install (Node Preparation): Checking size of device disk0:
Install (Node Preparation):    OK
Install (Node Preparation): Cleaning packages on device disk0:
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Complete
Install (Node Preparation): Checking free space on disk0:
Install (Node Preparation):    OK
Install (Node Preparation): Starting package and meta-data sync
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-rout-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-rout-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-lc-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-lc-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-fwdg-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-fwdg-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-admin-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-admin-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-base-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-base-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/c12k-os-mbi-3.8.0 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/c12k-os-mbi-3.8.0
Install (Node Preparation): Syncing package/meta-data contents: /disk0/instdb/ldpath 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/instdb/ldpath
Install (Node Preparation): Syncing package/meta-data contents: 
/disk0/instdb/ldpath.committed 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/instdb/ldpath.committed
Install (Node Preparation): Completed sync of all packages and meta-data.
Install (Node Preparation): Operation completed successfully. This node will now reload 
from disk0:.
Install (Node Preparation):    Please Wait...
Node 0/1/CPU0: insthelper: self-reset to use new boot image ...
 
   
System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 1024M found 
MPC7457 platform with 2097152 Kbytes of main memory
 
   
++++ Enabling L3 cache, flags = 0x50a38300 ..., old L3CR = 0xdca38340  done, new L3CR = 
0xdca38300 
 L2CR = 0xc0000000, MSSCR0 = 0x01188003 
J?###########################################
System page at phys:00023000 user:00023000 kern:00023000
Starting next program at v0026d6cc
              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 PRP, Version 3.8.0
Copyright (c) 2008 by Cisco Systems, Inc.
MBI-H: received a reload_node_req
MBI-H: got reload_node_req from slot 0
MBI-H: sent reload_node_ack to slot 0, rc =0
MBI-H: ready to reload
dumper_config: No HDD Controller found
MBI-H: reloading
 
   
System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 1024M found, Slot 2: 1024M found 
MPC7457 platform with 2097152 Kbytes of main memory
 
   
++++ Enabling L3 cache, flags = 0x50a38300 ..., old L3CR = 0xdca38340  done, new L3CR = 
0xdca38300 
 L2CR = 0xc0000000, MSSCR0 = 0x01188003 
J?###########################################
System page at phys:00023000 user:00023000 kern:00023000
Starting next program at v0026d6cc
              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 PRP, Version 3.8.0
Copyright (c) 2008 by Cisco Systems, Inc.
dumper_config: No HDD Controller found
Install (Node Preparation): Install device root is /disk0/
Install (Node Preparation): Trying device disk0:
Install (Node Preparation): Checking size of device disk0:
Install (Node Preparation):    OK
Install (Node Preparation): Checking free space on disk0:
Install (Node Preparation):    OK
Install (Node Preparation): Starting package and meta-data sync
Install (Node Preparation): Cleaning packages not in sync list
Install (Node Preparation):    Complete
Install (Node Preparation): Syncing package/meta-data contents: /disk0/instdb/ldpath 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/instdb/ldpath
Install (Node Preparation): Syncing package/meta-data contents: 
/disk0/instdb/ldpath.committed 
Install (Node Preparation):    Please Wait...
Install (Node Preparation):    Completed syncing: /disk0/instdb/ldpath.committed
Install (Node Preparation): Completed sync of all packages and meta-data.
 
   
 
   
ios con0/1/CPU0 is in standby

How to Perform a Pre-staged Migration: Example

The following example demonstrates how to perform disk swapping:

 
   
Router# show version
 
   
Cisco Internetwork Operating System Software 
IOS (tm) GS Software (C12KPRP-P-M), Version 12.0(32)SY7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Mon 29-Sep-08 14:44 by leccese
Image text-base: 0x00010000, data-base: 0x055D8000
 
   
ROM: System Bootstrap, Version 12.0(20061113:130348) [rarcher-CSCsg56342 1.18] RELEASE 
SOFTWARE
BOOTLDR: GS Software (C12KPRP-P-M), Version 12.0(32)SY7, RELEASE SOFTWARE (fc1)
 
   
 Router uptime is 4 minutes
Uptime for this control processor is 4 minutes
System returned to ROM by reload at 16:29:12 UTC Fri May 22 2009
System image file is "disk0:c12kprp-p-mz.120-32.SY7"
Network configuration file is "tftp://223.255.254.254/network-confg"
 
   
cisco 12410/PRP (MPC7457) processor (revision 0x00) with 1048576K bytes of memory.
MPC7457 CPU at 1263Mhz, Rev 1.1, 512KB L2, 2048KB L3 Cache
Last reset from sw reset
Channelized E1, Version 1.0.
 
   
1 Route Processor Card
2 Clock Scheduler Cards
5 Switch Fabric Cards
2 T1/E1 BITS controllers
1 Four Port Gigabit Ethernet/IEEE 802.3z controller (4 GigabitEthernet).
1 ISE 10G SPA Interface Card (12000-SIP-601)
3 Ethernet/IEEE 802.3 interface(s)
4 GigabitEthernet/IEEE 802.3 interface(s)
3 Packet over SONET network interface(s)
2043K bytes of non-volatile configuration memory.
 
   
1020600K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
65536K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2102
 
   
Router#
Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# config-register 0x00
Router(config)# exit
Router# write memory
 
   
Building configuration...
[OK]
Router#
 
   
############# ROUTER POWERED DOWN AND DISK/RP INSTALLED #############
 
   
 
   
System Bootstrap, Version 12.0(20061113:130348) [rarcher-CSCsg56342 1.18] RELEASE SOFTWARE
Copyright (c) 1994-2006 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 512M found, Slot 2: 512M found 
MPC7457 platform with 1048576 Kbytes of main memory
 
   
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon 1> unset BOOT
rommon 2> unset TURBOBOOT
rommon 3> BOOT=disk0:c12k-os-mbi-3.8.1/mbiprp-rp.vm
rommon 4> sync
rommon 5> reset
 
   
System Bootstrap, Version 12.0(20061113:130348) [rarcher-CSCsg56342 1.18] RELEASE SOFTWARE
Copyright (c) 19942006 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 512M found, Slot 2: 512M found 
MPC7457 platform with 1048576 Kbytes of main memory
 
   
rommon 6> boot disk0:c12k-os-mbi-3.8.1/mbiprp-rp.vm
 
   
++++ Enabling L3 cache, flags = 0x50a38300 ..., old L3CR = 0xdca38340  done, new L3CR = 
0xdca38300 
 L2CR = 0xc0000000, MSSCR0 = 0x01188003 
##########################################################################################
 
   
System page at phys:00023000 user:00023000 kern:00023000
Starting next program at v00229b24
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2 
tracelogger: _NTO_TRACE_SETRINGMODE succesfully enabled
              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 PRP, Version 3.8.1
Copyright (c) 2008 by Cisco Systems, Inc.
RP/0/8/CPU0:Jun  2 17:14:38.675: syslogd_helper: [87]: dsc_event_handler: Got SysMgr dSC 
event : 1
RP/0/8/CPU0:Jun  2 17:14:09.805 : dumper[56]:  No HDD Controller found by process dumper 
RP/0/8/CPU0:Jun  2 17:14:28.325 : sysmgr[88]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
RP/0/8/CPU0:Jun  2 17:14:28.742 : sysmgr[88]: %OS-SYSMGR-6-INFO : Please check process 
list for wd-critical-mon, it is marked as mdr_keep_thru, but not marked as mdr_shut_delay  
RP/0/8/CPU0:Jun  2 17:14:30.217 : dsc[167]: Memory Sanity Check Enabled
RP/0/8/CPU0:Jun  2 17:14:31.762 : wdsysmon[379]: %OS-RSVDPMEM-3-NO_MATCHING_STRING : 
Failed to find any line in /etc/platform_reserved_physmem containing string: pcds 
RP/0/8/CPU0:Jun  2 17:14:38.442 : dsc[167]: %PLATFORM-DSC-3-ERR_I_AM_DSC : Setting myself 
as DSC 
RP/0/8/CPU0:Jun  2 17:14:39.680 : redcon[320]: %OS-RSVDPMEM-3-NO_MATCHING_STRING : Failed 
to find any line in /etc/platform_reserved_physmem containing string: pcds 
RP/0/8/CPU0:Jun  2 17:15:06.188 : gsp[195]: %OS-gsp-6-INFO : 
gsp_process_create_gsp_grp_response: Error. send add node msg to writersgrp 
ens_admin_group (1) .   : pkg/bin/gsp : (PID=94278) :  -Traceback= 40154cd4 40135728 
40133a00 40108fb4 4010b508 4012aa80 4019eac0
RP/0/8/CPU0:Jun  2 17:15:11.673 : mbus_flash_driver[262]: No file system detected on  -- 
Please format 
RP/0/8/CPU0:Jun  2 17:15:13.323 : qsm[83]: %OS-QSM-3-ADMIN_ADD : (transition message) 
Detected admin plane add for admin_dumper_bootflash:. class: 0x80000031, svctype: 0x0, 
msgflags: 0x0 
RP/0/8/CPU0:Jun  2 17:15:18.439 : invmgr[205]: %PLATFORM-INVMGR-3-ERR_OBJECT_CREATE : Slot 
27. Error - power shelf bay object 
RP/0/8/CPU0:Jun  2 17:15:24.397 : qsm[83]: %OS-QSM-3-ADMIN_ADD : (transition message) 
Detected admin plane add for admin_dumper_bootflash:. class: 0x80000031, svctype: 0x0, 
msgflags: 0x0 
RP/0/8/CPU0:Jun  2 17:15:50.359 : sysldr[356]: %PLATFORM-SYSLDR-6-INFO : Waiting for 
startup config to be applied before booting LCs 
RP/0/8/CPU0:Jun  2 17:15:54.326 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/8/CPU0, state: IOS XR RUN  
 
   
 
   
Primary Clock is CSC_1
Fabric Clock is Redundant
Bandwidth Mode : Full Bandwidth
 
   
RP/0/8/CPU0:Jun  2 17:15:55.210 : sysldr[356]: %PLATFORM-SYSLDR-4-SPA_WARNING : slot5: 
Could not discover inserted SPA types, no response received to our mbus request 
RP/0/8/CPU0:Jun  2 17:16:00.219 : sysldr[356]: %PLATFORM-SYSLDR-5-OIRIN : OIR: Node 0/5/0 
inserted  
RP/0/8/CPU0:Jun  2 17:16:00.221 : sysldr[356]: %PLATFORM-SYSLDR-5-OIRIN : OIR: Node 0/5/1 
inserted  
RP/0/8/CPU0:Jun  2 17:17:49.917 : sysldr[356]: %PLATFORM-SYSLDR-6-INFO : Startup config 
applied, resuming work 
 
   
 
   
ios con0/8/CPU0 is now available
 
   
Press RETURN to get started.
 
   
RP/0/8/CPU0:Jun  2 17:17:52.547 : psarb[312]: %PLATFORM-PSARB-6-GO_ACTIVE : Card is going 
active. 
RP/0/8/CPU0:Jun  2 17:17:52.625 : sysldr[356]: %PLATFORM-SYSLDR-5-RESTART_REQ : Accepted 
restart request for slot 5 
RP/0/8/CPU0:Jun  2 17:17:52.625 : sysldr[356]: %PLATFORM-SYSLDR-5-RESTART_REQ : Accepted 
restart request for slot 1 
RP/0/8/CPU0:Jun  2 17:17:57.209 : invmgr[205]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 
0/1/CPU0 inserted  
RP/0/8/CPU0:Jun  2 17:17:57.306 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN  
RP/0/8/CPU0:Jun  2 17:18:02.184 : invmgr[205]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 
0/5/CPU0 inserted  
RP/0/8/CPU0:Jun  2 17:18:02.248 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: BRINGDOWN  
RP/0/8/CPU0:Jun  2 17:18:05.657 : invmgr[205]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 0/5/0 
inserted  
RP/0/8/CPU0:Jun  2 17:18:05.718 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/0, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:18:06.304 : invmgr[205]: %PLATFORM-INVMGR-5-OIRIN : OIR: Node 0/5/1 
inserted  
RP/0/8/CPU0:Jun  2 17:18:06.362 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/1, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:18:06.823 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/0, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:18:06.889 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/1, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:18:07.488 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/0, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:18:07.570 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/1, state: UNKNOWN  
 
   
 
   
SYSTEM CONFIGURATION IN PROCESS
 
   
The startup configuration for this device is presently loading.
This may take a few minutes. You will be notified upon completion.
 
   
Please do not attempt to reconfigure the device until this process is complete.
 
   
User Access Verification
 
   
Username: RP/0/8/CPU0:Jun  2 17:18:30.522 : sysldr[356]: %PLATFORM-SYSLDR-4-DOWN_REV : 
slot 5: fabric-downloader is down-rev (V6.0),  WARNING: Downrev fabloaders will result in 
long boot times 
RP/0/8/CPU0:Jun  2 17:18:46.004 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/8/CPU0 changed to ACTVRP   in state default  
RP/0/8/CPU0:Jun  2 17:18:56.291 : sysmgr[88]: %OS-SYSMGR-3-ERROR : ntpd(1) (jid 220) can 
not be restarted, entering slow-restart mode   
RP/0/8/CPU0:Jun  2 17:18:56.308 : sysmgr[88]: %OS-SYSMGR-3-ERROR : ntpd(220) (fail count 
0) will be respawned in 10 seconds  
RP/0/8/CPU0:Jun  2 17:18:56.323 : sysmgr[88]: %OS-SYSMGR-3-ERROR : ntpd(1) (jid 220) did 
not signal end of initialization   
 
   
SYSTEM CONFIGURATION COMPLETED
 
   
RP/0/8/CPU0:Jun  2 17:19:51.559 : cfgmgr-rp[136]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/8/0' has been restored. 
RP/0/8/CPU0:Jun  2 17:19:52.712 : ifmgr[197]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/8/CPU0/1, changed state to Down 
RP/0/8/CPU0:Jun  2 17:19:52.720 : ifmgr[197]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/8/CPU0/1, changed state to Down 
RP/0/8/CPU0:Jun  2 17:19:52.721 : ifmgr[197]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/8/CPU0/0, changed state to Down 
RP/0/8/CPU0:Jun  2 17:19:52.723 : ifmgr[197]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/8/CPU0/0, changed state to Down 
RP/0/8/CPU0:Jun  2 17:19:52.728 : cfgmgr-rp[136]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/8/0' has been restored. 
RP/0/8/CPU0:Jun  2 17:19:52.789 : ifmgr[197]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/8/CPU0/1, changed state to Up 
RP/0/8/CPU0:Jun  2 17:19:52.792 : ifmgr[197]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
MgmtEth0/8/CPU0/0, changed state to Up 
RP/0/8/CPU0:Jun  2 17:19:52.800 : ifmgr[197]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/8/CPU0/1, changed state to Up 
RP/0/8/CPU0:Jun  2 17:19:52.835 : ifmgr[197]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface MgmtEth0/8/CPU0/0, changed state to Up 
 
   
RP/0/8/CPU0:IOX-R2#RP/0/8/CPU0:Jun  2 17:20:16.524 : sysldr[356]: 
%PLATFORM-SYSLDR-4-MBUS_IN_ROM : slot 1: mbus agent in ROM, downloading RAM mbus fw v2.56 
... 
RP/0/8/CPU0:Jun  2 17:20:45.222 : sysldr[356]: %PLATFORM-SYSLDR-4-DOWN_REV : slot 1: 
fabric-downloader is down-rev (V7.3),  WARNING: Downrev fabloaders will result in long 
boot times 
RP/0/8/CPU0:Jun  2 17:21:24.508 : ssm_process[343]: %OS-SSM-6-SYSDB_BLOCK_RECOVER : Sysdb 
service becomes available, update configuration. 
RP/0/8/CPU0:Jun  2 17:21:25.141 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/0, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:21:25.147 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/1, state: UNKNOWN  
 
   
RP/0/8/CPU0:IOX-R2#RP/0/8/CPU0:Jun  2 17:23:39.367 : sysldr[356]: 
%PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 1 is now running IOX 
RP/0/8/CPU0:Jun  2 17:23:39.385 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/1/CPU0 changed to IOX RUN  in state default  
RP/0/8/CPU0:Jun  2 17:23:39.453 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: IOS XR RUN  
RP/0/8/CPU0:Jun  2 17:23:43.978 : sysldr[356]: %PLATFORM-SYSLDR-5-LC_ENABLED : LC in slot 
5 is now running IOX 
RP/0/8/CPU0:Jun  2 17:23:43.997 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/5/CPU0 changed to IOX RUN  in state default  
RP/0/8/CPU0:Jun  2 17:23:44.009 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/CPU0, state: IOS XR RUN  
RP/0/8/CPU0:Jun  2 17:23:44.015 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/0, state: UNKNOWN  
RP/0/8/CPU0:Jun  2 17:23:44.019 : invmgr[205]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/5/1, state: UNKNOWN  
LC/0/1/CPU0:1:42: sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/1/CPU0:1:44: sysmgr[81]: %OS-SYSMGR-6-INFO : Please check process list for 
wd-critical-mon, it is marked as mdr_keep_thru, but not marked as mdr_shut_delay  
LC/0/1/CPU0:1:49: wdsysmon[265]: %OS-RSVDPMEM-3-OPEN_FAIL : Open of 
/etc/platform_reserved_physmem failed. Error No such file or directory 
LC/0/1/CPU0:Jun  2 17:24:02.945 : timesync_client[257]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 17:24:02.748 UTC Tue Jun 02 
2009 
LC/0/1/CPU0:2:15: mbus_flash_driver[185]: No file system detected on  -- Please format 
LC/0/5/CPU0:2:6: sysmgr[81]: %OS-SYSMGR-5-NOTICE : Card is COLD started  
LC/0/5/CPU0:2:8: sysmgr[81]: %OS-SYSMGR-6-INFO : Please check process list for 
wd-critical-mon, it is marked as mdr_keep_thru, but not marked as mdr_shut_delay  
LC/0/5/CPU0:2:15: wdsysmon[270]: %OS-RSVDPMEM-3-OPEN_FAIL : Open of 
/etc/platform_reserved_physmem failed. Error No such file or directory 
LC/0/5/CPU0:Jun  2 17:24:03.173 : timesync_client[262]: 
%PLATFORM-TIMESYNC_CLIENT-6-TIME_SET : Local clock is set to 17:24:02.748 UTC Tue Jun 02 
2009 
LC/0/5/CPU0:Jun  2 17:24:18.295 : gsr_lclm[161]: 
%LICENSE-LCLICMGR-3-RATE_MODE_SECURITY_FAIL :          WARNING!!! The module in node 
0/5/CPU0 in this router may not be a genuine Cisco product. Cisco warranties and support 
programs only apply to genuine Cisco products. If Cisco determines that your insertion of 
non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules 
into a Cisco product is the cause of a support issue, Cisco may deny support under your 
warranty or under a Cisco support program such as SmartNet. 
LC/0/5/CPU0:Jun  2 17:24:05.992 : mbus_flash_driver[189]: No file system detected on  -- 
Please format 
 
   
RP/0/8/CPU0:IOX-R2#show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/1/CPU0        L3LC Eng 3      GE-4            IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        L3LC Eng 5+     Jacket Card     IOS XR RUN      PWR,NSHUT,MON
0/5/0           SPA             SPA-2XOC48POS/R UNKNOWN         PWR,NSHUT
0/5/1           SPA             SPA-4XT3/E3     UNKNOWN         PWR,NSHUT
0/8/CPU0        PRP(Active)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/8/CPU0:IOX-R2#LC/0/1/CPU0:Jun  2 17:24:54.239 : qos_ea[227]: %QOS-QOSEA-6-INFO : 
QoSEA-Info: qos_ea_acl_deny_init[5007]: acl deny admin state->0  
 
   
RP/0/8/CPU0:IOX-R2#
RP/0/8/CPU0:IOX-R2#
telnet> 
RP/0/8/CPU0:IOX-R2#show ver
Cisco IOS XR Software, Version 3.8.1[00]
Copyright (c) 2008 by Cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 12.0(20061113:130348) [rarcher-CSCsg56342 1.18] RELEASE 
SOFTWARE
Copyright (c) 1994-2006 by cisco Systems,  Inc.
 
   
IOX-R2 uptime is 11 minutes
System image file is "disk0:c12k-os-mbi-3.8.1/mbiprp-rp.vm"
 
   
cisco 12410/PRP (7457) processor with 1048576K bytes of memory.
7457 processor at 1266Mhz, Revision 1.1
 
   
1 Cisco 12000 4 Port Gigabit Ethernet Controller (4 GigabitEthernet)
1 Cisco 12000 Series SPA Interface Processor-601/501/401
1 Cisco 12000 Series Performance Route Processor
3 Ethernet/IEEE 802.3 interface(s)
1016k bytes of non-volatile configuration memory.
1020144k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).
65536k bytes of Flash internal SIMM (Sector size 256k).
 
   
Boot device on node 0/1/CPU0 is mem:
Package active on node 0/1/CPU0:
c12k-lc, V 3.8.1[00], Cisco Systems, at disk0:c12k-lc-3.8.1
    Built on Thu Nov  6 13:09:43 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-fwdg, V 3.8.1[00], Cisco Systems, at disk0:c12k-fwdg-3.8.1
    Built on Thu Nov  6 13:08:42 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-admin, V 3.8.1[00], Cisco Systems, at disk0:c12k-admin-3.8.1
    Built on Thu Nov  6 13:07:54 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-base, V 3.8.1[00], Cisco Systems, at disk0:c12k-base-3.8.1
    Built on Thu Nov  6 13:06:24 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-os-mbi, V 3.8.1[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.1
    Built on Thu Nov  6 13:00:46 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
Boot device on node 0/5/CPU0 is mem:
Package active on node 0/5/CPU0:
c12k-lc, V 3.8.1[00], Cisco Systems, at disk0:c12k-lc-3.8.1
Built on Thu Nov  6 13:09:43 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-fwdg, V 3.8.1[00], Cisco Systems, at disk0:c12k-fwdg-3.8.1
    Built on Thu Nov  6 13:08:42 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-admin, V 3.8.1[00], Cisco Systems, at disk0:c12k-admin-3.8.1
    Built on Thu Nov  6 13:07:54 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-base, V 3.8.1[00], Cisco Systems, at disk0:c12k-base-3.8.1
    Built on Thu Nov  6 13:06:24 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-os-mbi, V 3.8.1[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.1
    Built on Thu Nov  6 13:00:46 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
Configuration register on node 0/8/CPU0 is 0x0
Boot device on node 0/8/CPU0 is disk0:
Package active on node 0/8/CPU0:
c12k-rout, V 3.8.1[00], Cisco Systems, at disk0:c12k-rout-3.8.1
Built on Thu Nov  6 13:10:32 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-lc, V 3.8.1[00], Cisco Systems, at disk0:c12k-lc-3.8.1
    Built on Thu Nov  6 13:09:43 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-fwdg, V 3.8.1[00], Cisco Systems, at disk0:c12k-fwdg-3.8.1
    Built on Thu Nov  6 13:08:42 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-admin, V 3.8.1[00], Cisco Systems, at disk0:c12k-admin-3.8.1
    Built on Thu Nov  6 13:07:54 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-base, V 3.8.1[00], Cisco Systems, at disk0:c12k-base-3.8.1
    Built on Thu Nov  6 13:06:24 UTC 2008
    By edde-bld1 in /auto/srcarchive1/production/3.8.1/c12k/workspace for c2.95.3-p8
 
   
c12k-os-mbi, V 3.8.1[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.1
    Built on Thu Nov  6 13:00:46 UTC 2008
 
   

Troubleshooting a Failed Migration: Examples

Upgrading the Mbus Firmware: Example

Upgrading the Fabric Downloader: Example

Verifying the Field-Programmable Devices in All Slots: Example

Reverting to Cisco IOS from Cisco IOS XR Software: Example

Upgrading the Mbus Firmware: Example

The upgrade of the Mbus illustrated in the following example occurred because Cisco IOS XR software detected that the Mbus version was not current; it therefore displayed the following message during startup:

Router:Jun  8 18:33:33.089 : mbus-prp[62]: %PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV : slot 
17: mbus rom agent is down-rev (V3.48), suggest upgrade to current (V3.7). Use the 
"upgrade mbus" CLI in admin mode.
 
   

To address this, the user issued the following command:

RP/0/0/CPU0:router(admin)# upgrade mbus location all 
 
   
Upgrading the MBUS agent rom on all slots 
Router:July 12 13:37:25.967 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 0, DOWNLOAD_SUCCESS  
Router:July 12  13:37:43.718 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 0, PROGRAM_ROM SUCCESS  
Router:July 12  13:37:52.264 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 1, DOWNLOAD_SUCCESS  
Router:July 12  13:38:12.543 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 1, PROGRAM_ROM SUCCESS  
Can not upgrade, slot 2 is empty. 
RP/0/0/CPU0:July 12  13:38:21.060 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 3, DOWNLOAD_SUCCESS  
RP/0/0/CPU0:July 12  13:38:31.452 : upgrade_mbus[65709]: %PLATFORM-MBUS-6-API_INFO_DUMP : 
download status slot 3, PROGRAM_ROM SUCCESS  
Slot 4 does not need upgrade. 
Can not upgrade, slot 5 is empty.
 
   

Verifying the Field-Programmable Devices in All Slots: Example

The following example illustrates a verification of the uprgrade status of field-programmable devices (FPD) in all slots. The column at farthest right in the output example (Upg/Dng?) indicates whether the FPD in a particular slot requires an upgrade or a downgrade.

RP/0/0/CPU0:router(admin)# show hw-module fpd location all
 
   
Tue Jun  2 03:38:35.154 PST 
 
   
===================================== ==========================================
                                      Existing Field Programmable Devices
                                      ==========================================
                                        HW                       Current SW Upg/
Location     Card Type                Version Type Subtype Inst   Version   Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/0/0        SPA-5X1GE-V2               1.2   spa  fpga    0       1.10     No 
--------------------------------------------------------------------------------
0/0/1        SPA-4XT3/E3                1.0   spa  fpga    1       1.1      No 
                                              spa  rommon  1       2.12     No 
                                              spa  fpga2   1       1.4      No 
                                              spa  fpga3   1       1.4      No 
--------------------------------------------------------------------------------
0/0/2        SPA-4XOC12-POS             1.0   spa  fpga    2       1.0      No 
--------------------------------------------------------------------------------
0/0/3        SPA-8XCHT1/E1              1.0   spa  fpga    3       2.8      No 
                                              spa  rommon  3       2.12     No 
--------------------------------------------------------------------------------
0/1/1        SPA-1XCHOC12/DS0           1.0   spa  rommon  1       2.2      No 
                                              spa  fpga    1       1.7      No 
                                              spa  fpga2   1       1.0      No 
--------------------------------------------------------------------------------
0/2/0        SPA-10X1GE-V2              1.1   spa  fpga    0       1.10     No 
--------------------------------------------------------------------------------
0/2/1        SPA-2CHT3-CE-ATM           1.0   spa  fpga    1       1.19     Yes
                                              spa  rommon  1       1.2      Yes
                                              spa  fpga2   1       1.8      Yes
--------------------------------------------------------------------------------
0/3/0        SPA-5X1GE-V2               1.1   spa  fpga    0       1.10     No 
--------------------------------------------------------------------------------
0/3/1        SPA-2XOC48POS/RPR          1.0   spa  fpga    1       1.0      No 
--------------------------------------------------------------------------------
0/4/0        SPA-OC192POS-XFP           2.1   spa  fpga    0       1.2      No 
--------------------------------------------------------------------------------
0/4/1        SPA-1XCHOC48/DS3           1.0   spa  rommon  1       2.2      No 
                                              spa  fpga    1       1.7      No 
                                              spa  fpga2   1       1.0      No 
                                              spa  fpga3   1       1.0      No 
--------------------------------------------------------------------------------
0/4/2        SPA-8X1FE                  1.2   spa  fpga    2       1.1      No 
--------------------------------------------------------------------------------
0/5/0        SPA-8X1GE-V2               1.1   spa  fpga    0       1.10     No 
--------------------------------------------------------------------------------
0/5/1        SPA-4XOC3-POS-V2           1.0   spa  fpga    1       1.0      No 
--------------------------------------------------------------------------------
0/8/CPU0     E3-OC3-ATM-4             255.255 lc   fpga    0   40977.0      No 
                                              lc   fpga2   0   40971.0      No 
                                              lc   fpga3   0   41091.0      No 
                                              lc   fpga4   0   45584.0      Yes
--------------------------------------------------------------------------------
0/10/0       SPA-8XCHT1/E1              1.5   spa  fpga    0       2.8      No 
                                              spa  rommon  0       2.12     No 
--------------------------------------------------------------------------------
0/10/1       SPA-IPSEC-2G-2             1.0   spa  rommon  1       1.1      No 
                                              spa  fpga    1       1.22     No 
                                              spa  fpga2   1       1.1      No 
--------------------------------------------------------------------------------
0/10/2       SPA-4XCT3/DS0              1.2   spa  fpga    2       2.8      No 
                                              spa  rommon  2       2.12     No 
                                              spa  fpga2   2       1.4      No 
--------------------------------------------------------------------------------
0/11/CPU0    E3-OC3-ATM-4             255.255 lc   fpga    0   40977.0      No 
                                              lc   fpga2   0   40971.0      No 
                                              lc   fpga3   0   41091.0      No 
                                              lc   fpga4   0   45584.0      Yes
--------------------------------------------------------------------------------
0/12/1       SPA-4XT3/E3                1.1   spa  fpga    1       1.1      No 
                                              spa  rommon  1       2.12     No 
                                              spa  fpga2   1       1.4      No 
                                              spa  fpga3   1       1.4      No 
--------------------------------------------------------------------------------
0/12/3       SPA-1XCHSTM1/OC3           2.0   spa  fpga    3       1.8      No 
                                              spa  rommon  3       2.12     No 
                                              spa  fpga2   3       1.4      No 
-------------------------------------------------------------------------------

Upgrading the Fabric Downloader: Example

The upgrade of the fabric downloader firmware illustrated in this example occurred, because the following messages appeared during the startup phase of the Cisco IOS XR software installation:

RP/0/0/CPU0:Apr 1 07:17:08.495: sysldr[276]:%SYSLDR-4-DOWN_REV: slot 3: fabric-downloader 
is down-rev (V5.6), consult technical support. WARNING: Downrev fabloaders will result in 
long boot times.
RP/0/0/CPU0:Apr  1 07:17:08.980 : sysldr[276]: %SYSLDR-4-DOWN_REV : slot 4: 
fabric-downloader is down-rev (V5.6), consult technical support. WARNING: Downrev 
fabloaders will result in long boot times.
 
   

If it detects that the fabric downloader firmware version is not current, Cisco IOS XR software displays the previous message during the startup process.

To address this, issue the following commands:

RP/0/0/CPU0:router# admin 
RP/0/0/CPU0:router(admin)# upgrade ?
 
   
  all                upgrade all rom images on the LC
  fabric-downloader  upgrade the fabric-downloader on the LC
  hw-module          Upgrade h/w module
  mbus               mbus agent rom
  rommon             upgrade the rommon on the LC
 
   
RP/0/0/CPU0:router(admin)# upgrade fabric-downloader all
 
   
This will take around 7-10 minutes for a full chassis.
Ensure that GSR is not power cycled during the upgrade.
Premature termination of this command may render the GSR inoperable.
Please consult the documentation for more information.
Continue ? [no]: yes
FL-VER: SysDB get failed for 16/fl_version
Fail to update Fab Loader Rom version in SysDb for 1
Downloading ALPHA fabric loader v6.4 to slot 3
 
   
========= Line Card (Slot 3) =========
Upgrading linecard fabric-downloader
Erasing sectors: eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Programming image: ppppppppppppppppppppppppp
Verifying image: vvvvvvvvvvvvvvvvvvvvvvvvv
Upgraded linecard fabric-downloader successfully
Downloading ALPHA fabric loader v6.4 to slot 4
 
   
========= Line Card (Slot 4) =========
Upgrading linecard fabric-downloader
LC/0/4/CPU0:Apr 27 13:36:40.951 : lc_rom_upgrade[159]: %PLATFORM-UPGRADE-4-FABRI
C_UPGRADE : fabric-downloader upgrade is not required : flash version:6.4 >= new
 version:6.4 
 
   
Linecard fabric-downloader upgrade is not required : Newer revision of fabric loader 
present in rom

Reverting to Cisco IOS from Cisco IOS XR Software: Example

This example illustrates the output from "How to Perform a Pre-staged Migration" procedure, Step 4:

RP/0/0/CPU0:Router(admin)# reload location all
 
   
 
   
Preparing system for backup. This may take a few minutes [done]
Proceed with reload? [confirm]
 
   
RP/0/0/CPU0:Jul  2 18:44:47.926 : sysldr[392]: %PLATFORM-SYSLDR-5-REST
ART_REQ : Accepted restart request for slot 2 
RP/0/0/CPU0:Jul  2 18:44:47.974 : alphadisplay[103]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/2/CPU0 changed to     BRDN in state default  
RP/0/0/CPU0:Jul  2 18:44:47.980 : invmgr[214]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/2/CPU0, state: BRINGDOWN  
RP/0/0/CPU0:Jul  2 18:44:47.985 : invmgr[214]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/2/0, state: UNKNOWN  
RP/0/0/CPU0:Jul  2 18:44:47.989 : invmgr[214]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/2/1, state: UNKNOWN  
RP/0/0/CPU0::This node received reload command. Reloading in 5 secs
RP/0/0/CPU0:Jul  2 18:44:51.366 : invmgr[214]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/2/0, state: UNKNOWN  
RP/0/0/CPU0:Jul  2 18:44:51.374 : invmgr[214]: %PLATFORM-INVMGR-6-NODE_STATE_CHANGE : 
Node: 0/2/1, state: UNKNOWN  
 
   
System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE
Copyright (c) 1994-2004 by cisco Systems, Inc.
 
   
DRAM DIMM Slot 1: 2048M found, Slot 2: Empty 
MPC7457 platform with 2097152 Kbytes of main memory

This example illustrates the output from Step 8 in the "How to Perform a Pre-staged Migration" procedure, showing return to the Cisco IOS operating system, including Step 9, which is commited from a Cisco IOS node:

rommon# boot disk1:c12kprp-p-mz.120-32.SY2.bin
 
   
Self decompressing the image : 
...
[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-P-M), Version 12.0(32)SY2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Fri 01-Dec-06 14:41 by wwsmith
Image text-base: 0x00010000, data-base: 0x05380000
cisco 12406/PRP (MPC7457) processor (revision 0x00) with 2097152K bytes of memory.
MPC7457 CPU at 1263Mhz, Rev 1.2, 512KB L2, 2048KB L3 Cache
Last reset from sw reset
Channelized E1, Version 1.0.
 
   
1 Route Processor Card
1 Clock Scheduler Card
3 Switch Fabric Cards
1 ISE 10G SPA Interface Card (12000-SIP-601)
3 Ethernet/IEEE 802.3 interface(s)
4 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).
1000944K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
65536K bytes of Flash internal SIMM (Sector size 256K).
SETUP: new interface POS2/0/0 placed in "shutdown" state
SETUP: new interface POS2/0/1 placed in "shutdown" state
SETUP: new interface POS2/0/2 placed in "shutdown" state
SETUP: new interface POS2/0/3 placed in "shutdown" state
Press RETURN to get started!
User Access Verification
Username: cisco
Password: 
 
   
Router:# upgrade all all force

Additional References

Related Documents

Related Topic
Document Title

Prerequisites for migration to Cisco IOS XR software.

Release Notes for Cisco IOS XR Software for the targeted release

Getting started procedures for Cisco IOS XR software.

Cisco IOS XR Getting Started Guide

Using ROM Monitor.

Cisco CRS-1 Carrier Router System Getting Started Guide, Appendix-A: ROM Monitor Guide

Pre-staged migration methods and commands

Cisco IOS XR System Management Configuration Guide and Cisco IOS XR System Management Command Reference


Technical Assistance

Description
Link

The Cisco Support website contains thousands of pages of searchable technical content, including links to products, technologies, and solutions, technical tips, and tools.

Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport