Guest

Cisco Carrier Routing System

CRS-PRP Routing Processor Migration

  • Viewing Options

  • PDF (550.3 KB)
  • Feedback

Table Of Contents

CRS-PRP Routing Processor Migration

Method 1 - Configuration & Package Synchronization Method

Method 1 - Single Chassis Prerequisites

Method 1 - Single Chassis Upgrade Procedure

Method 1 - Multishelf Prerequisites

Method 1 - Multishelf Upgrade Procedure

Method 1 - Caveats

Method 2 - Turboboot of the Cisco CRS-PRP Route Processor

Method 2 - Single Chassis Prerequisites

Method 2 - Single Chassis Cisco CRS-PRP Route Processor Turboboot Procedure

Method 3 - Routing Processor Swap Method

Method 3 - Single Chassis Prerequisites:

Method 3 - Single Chassis Procedure:

Backout Procedure


CRS-PRP Routing Processor Migration


Product Number: CRS-PRP=

Document Order Number: OL-24839-01

This document describes the following three methods available to migrate from the Cisco RP-A or RP-B Routing Processor to the new Cisco CRS-PRP Routing Processor.

Method 1 - Configuration & Package Synchronization Method

Method 2 - Turboboot of the Cisco CRS-PRP Route Processor

Method 3 - Routing Processor Swap Method

There is also a section describing how to return to using the Cisco RP-B Routing Processor after having upgraded to the new Cisco CRS-PRP Routing Processor.

Backout Procedure


Note While Method #1 does not explicitly require the use of a Console Port it is highly recommended to have one available during the migration.


Method 1 - Configuration & Package Synchronization Method

This method performs configuration and package synchronization from the active Cisco RP-A or RP-B Route Processor to the Cisco CRS-PRP Route Processor. The key advantage of this procedure is that the existing configurations are automatically synchronized to the new Cisco CRS-PRP Route Processor. They do not need to be prepared outside the system. This makes the procedure fairly simple and reliable.


Note Note that when using Method 1 the crypto keys are not synchronized. The crypto keys must be regenerated after the Cisco CRS-PRP is booted.


The disadvantage of this procedure is that it requires, as a pre-requisite, the upgrading of the RP-A or RP-B system to the target Cisco IOS XR software release which supports the Cisco CRS-PRP (Cisco IOS XR software release 4.0.2 or higher). Therefore, the overall time required to complete the image upgrade and hardware migration is high compared to the other methods.

Method 1 - Single Chassis Prerequisites

The Cisco IOS XR software release running on the Cisco RP-A or RP-B Route Processor must be Cisco IOS XR software release 4.0.2 or higher.


Note The upgrade to the corresponding Cisco IOS XR software version is a standard upgrade procedure. This procedure is described in the upgrade documents in PDF available online here:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html


Before upgrading to the Cisco IOS XR software release that supports the Cisco CRS-PRP Route Processor, confirm that the appropriate ROMMON and FPGA images as per the target Cisco IOS XR software release are already installed. The compatibility matrix is available at:

http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/SoftwareFirmwareCompatibilityMatrix.pdf

Enter the following command to check the FPD of the running hardware modules on the router:

(admin) show hw-module fpd location all
 
 

If the Auto-FPD upgrade is performed as part of the image upgrade procedure (Pre-Requisite #1), then ROMMON and FPGA upgrades on the line cards and fabric cards are already taken care of (all will have been updated to the latest version). If not, you need to upgrade the FPD.

Detailed procedures for ROMMON upgrade is detailed in the Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers section in the Cisco IOS XR ROM Monitor Guide for the Cisco CRS Router document online.

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.0/rommon/configuration/guide/rm40ucrs.html

Verify that the standby Cisco RP-A or RP-B Route Processor is in ready state by executing the following command:

RP/0/RP0/CPU0:CRS-1(admin)#show redundancy summary
 
 
Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
 
 

The status of the standby Cisco RP-A or RP-B Route Processor is indicated in parentheses, next to the node identifier. The nonstop routing (NSR) status is indicated following the term NSR. Possible values are Ready and Not ready.

Ensure that you have a short LC to LC Single Mode fiber cable available (for connecting the active Cisco RP-A or RP-B Route Processor to the newly installed Cisco CRS-PRP Route Processor). Refer to Figure 1 for an example of this cable.

Figure 1 LC Type Cables

Method 1 - Single Chassis Upgrade Procedure


Step 1 Connect console cables to both the Active and the Standby Cisco RP-B or RP-A Route Processor console ports

Step 2 Remove the Standby Cisco RP-B or RP-A Route Processor and replace it with the Cisco CRS-PRP Route Processor.

Step 3 Reconnect the console cable on newly inserted Cisco CRS-PRP Route Processor. Issue the control-break key combination to hold the Cisco CRS-PRP Route Processor in ROMMON mode. Execute the following ROMMON commands to unset the BOOT variable.

 
 
rommon1>unset BOOT
rommon1>confreg 0x102
rommon1>sync
rommon1>reset
 
 

Note The PRP is shipped with a pre-installed IOS-XR image. Use this procedure to install the required target IOS-XR image if it is different than the shipped pre-installed IOS-XR image.


Step 4 Attach a short LC to LC Single Mode fiber cable between the Active Cisco RP-B or RP-A Route Processor and the newly installed Cisco CRS-PRP Route Processor. Either the CE (Control Ethernet) port 0 or CE (Control Ethernet) port 1 can be used. The cable is required because the backplane link is not compatible between the Cisco RP-B or RP-A Route Processor and the newly installed Cisco CRS-PRP Route Processor.

After you connect the cable, the newly installed Cisco CRS-PRP Route Processor synchronizes the Cisco IOS XR software packages on the Cisco RP-B or RP-A Route Processor.

Next, the Active Cisco RP-B or RP-A Route Processor synchronizes the configuration by copying it to the newly installed Cisco CRS-PRP Route Processor.

a. Package synchronization begins. After the package synchronization completes successfully, the Cisco CRS-PRP Route Processor will self-reload from the boot device, as shown in this example:

Nov 05 01:58:56.556 : Install (Node Preparation):    Please wait...
Nov 05 01:58:56.610 : Install (Node Preparation):    Completed syncing: 
/disk0/instdb/aliases/hfr-mini-px-4.0.1.50I
Nov 05 01:58:56.860 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
Nov 05 01:59:15.429 : Install (Node Preparation): Operation completed successfully. 
This node will now reload from disk0:.
Nov 05 01:59:15.429 : Install (Node Preparation):    Please wait...
Node 0/RP1/CPU0: insthelper: self-reset to use new boot image ...
 
 
 
 

b. After the self-reload of the Cisco CRS-PRP Route Processor, there is a quick re-synchronization of all the packages and metadata as part of the complete package synchronization operation.

c. The configuration synchronization is triggered immediately after the re-synchronization of the packages and metadata. However, the newly-installed Cisco CRS-PRP Route Processor never enters Standby Ready state when paired with the Cisco RP-A or RP-B Route Processor. There will be messages on the Cisco CRS-PRP Route Processor console as shown in this example:

Nov 05 02:01:53.969 : Install (Node Preparation):    Completed syncing: 
/disk0/instdb/aliases/hfr-mini-px-4.0.1.50I
Nov 05 02:01:53.969 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
Nov 05 02:02:04.442 : PRP upgrade syncing configuration from dSC:   Please wait ...
Nov 05 02:02:50.220 : PRP upgrade configure sync success, src: 
/net/node0_RP0_CPU0/disk0:/config/, dest: /net/node0_RP1_CPU0/disk0:/config/
 
 

The alpha display on the Cisco CRS-PRP Route Processor now displays the SYNC READY state. The one caveat is that you cannot synchronize the crypto keys from the Active Route Processor, if, for instance, SSH is used. The Cisco RP-A or RP-B also indicates the synchronization ready state of the Cisco CRS-PRP Route Processor. You can confirm this status by executing the show hfr command.

RP/0/RP0/CPU0:dSC-RP-B(admin)#show hfr | inc 0/RP
0/RP0/CPU0    RP(Active)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0    RP(Standby)       N/A              SYNC-READY      PWR,NSHUT,MON
RP/0/RP0/CPU0:dSC-RP-B(admin)#
 
 

Step 5 Verify that the package and configuration synchronization is complete by observing the SYNC READY state indication on the alpha display on the Cisco CRS-PRP Route Processor.

Step 6 Remove the LC fiber cable.

Step 7 Eject and remove the Active Cisco RP-A or RP-B Route Processor.


Note You must ensure that the Active Cisco RP-A or RP-B Route Processor is removed completely immediately after the completion of the configuration synchronization and immediately after the LC fiber cable is removed. Otherwise the whole process from steps 3 to 5 must be repeated after waiting15 minutes from the completion of configuration synchronization.


Step 8 The Cisco CRS-PRP Route Processor front panel includes an OIR push button. Press the OIR push button on the Cisco CRS-PRP Route Processor front panel to initiate the OIR process.

Initiating the OIR process by pressing the OIR push button avoids the loss of card information caused by a surprise extraction.

If a Cisco CRS-PRP Route Processor is extracted without initiating the OIR process (that is, by a surprise extraction), the saving of logs or other important information is not possible. Although surprise extractions are supported, using the OIR process allows you to save important card information and logs.

When the OIR process is complete, the OIR Ready LED glows solidly to indicate that the Cisco CRS-PRP Route Processor is ready for extraction.

Step 9 Extract the Cisco CRS-PRP Route Processor.

Step 10 Reinsert the Cisco CRS-PRP Route Processor. This causes a reload of the entire system. Since there is only one Route Processor in the system, the newly-installed Cisco CRS-PRP Route Processor becomes the Active Route Processor.

Step 11 Use the Status LED, located on the Cisco CRS-PRP Route Processor faceplate, to verify the correct installation of the Cisco CRS-PRP Route Processor:

a. Status LED is Green—The card is correctly installed and operating properly.

b. Status LED is Blinking Yellow—A problem exists on the card.

c. Status LED is Off—The card status is unknown. Verify that the card is installed correctly. Verify also that there is power to the card by checking the indicators on the power shelf.

The primary Cisco CRS-PRP Route Processor is functioning correctly when the alphanumeric LED displays "ACTV RP".

When the Cisco CRS-PRP Route Processor is in primary mode (that is, the alphanumeric LED displays ACTV RP), the board is executing control processing functions and is not in a secondary or standby role.

Step 12 After the reload completes and the Cisco CRS-PRP Route Processor has become the Active Route Processor, insert the second (Standby) Cisco CRS-PRP Route Processor. This will start the Software package synchronization, followed with the self-reload and configuration synchronization.

Step 13 If the newly-inserted second (Standby) Cisco CRS-PRP Route Processor does not start booting enter ROMMON and execute the following three commands listed below to modify the Config-register setting:

rommon1>confreg 0x102
rommon1>sync
rommon1>reset
 
 

Step 14 Verify the Software package synchronization, followed with the self-reload and configuration synchronization by observing the following display:

Nov 09 01:25:22.797 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
RP/0/RP0/CPU0:Nov  9 01:25:33.237: syslogd_helper: [92]: dsc_event_handler: Got SysMgr dSC 
event : 16
RP/0/RP0/CPU0:Nov  9 01:25:33.237: syslogd_helper: [92]: dsc_event_handler: syslogd_helper 
already received non DSC event 16
 
 

The Standby Cisco CRS-PRP Route Processor now comes up in Standby Ready state. You can confirm this when the following syslog message displays:

RP/0/RP1/CPU0:Nov  4 08:13:03.505 : redcon[308]: %HA-REDCON-1-STANDBY_READY : standby card 
is ready 
 
 

Step 15 Verify that the Standby Cisco CRS-PRP Route Processor has attained NSR Ready State by executing the show redundancy summary command:

RP/0/RP0/CPU0:router# show redundancy summary
  
  Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
 
 

When the Standby Cisco CRS-PRP Route Processor is in NSR Ready State, the system is fully up and fully redundant.


Method 1 - Multishelf Prerequisites

The version of Cisco IOS XR software running on the Cisco RP-A or the Cisco RP-B Route Processor must be Cisco IOS XR software version 4.0.2 or higher.


Note The upgrade procedure to the corresponding Cisco IOS XR software version is a standard upgrade procedure and can be followed by accessing the upgrade documents in PDF available online here:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html


Before upgrading to the Cisco IOS XR software release that supports the Cisco CRS-PRP Route Processor, confirm that the appropriate ROMMON and FPGA images as per the target Cisco IOS XR software release are already installed. The compatibility matrix is available at:

http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/SoftwareFirmwareCompatibilityMatrix.pdf

Enter the following command to check the FPD of the running hardware modules on the router:

(admin) show hw-module fpd location all
 
 

If the Auto-FPD upgrade is performed as part of the image upgrade procedure (Pre-Requisite #1), then ROMMON and FPGA upgrades on the line cards and fabric cards are already taken care of (all will have been updated to the latest version). If not, you will need to upgrade the FPD.

Detailed procedures for ROMMON upgrade are available online in the Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers section of the Cisco IOS XR ROM Monitor Guide for the Cisco CRS Router document.

Verify that the standby Cisco RP-A or Cisco RP-B Route Processor is in ready state by executing the show redundancy summary command:

RP/0/RP0/CPU0:CRS-1(admin)#show redundancy summary
 
 
Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
 
 

The status of the standby Cisco RP-A or Cisco RP-B Route Processor is indicated in parentheses next to the node identifier. The nonstop routing (NSR) status is indicated following the term NSR. Possible values are Ready and Not ready.

Ensure that you have a short LC to LC Single Mode fiber cable available (for connecting the active Cisco RP-A or Cisco RP-B Route Processor to the newly-installed Cisco CRS-PRP Route Processor). Refer to Figure 2 below for an example of this cable.

Figure 2 LC Type Cables

Method 1 - Multishelf Upgrade Procedure


Step 1 Place all nDSC Route Processors into ROMMON state by setting the config register to 0x0 on each nDSC, followed by a reload of one rack at a time.


Note The Fabric Chassis must not be switched off and needs to remain in operation while these commands are executed.


RP/1/RP0/CPU0:CRS-1(admin)#config-register 0x0
Successfully set config-register to 0x0 on node 1/RP0/CPU0
Successfully set config-register to 0x0 on node 1/RP1/CPU0
RP/1/RP0/CPU0:CRS-1(admin)#reload rack <dsc-rack#>
 
 

Step 2 On the DSC, disconnect the Control Ethernet cables from the Standby Route Processor, remove the Standby Cisco RP-A or Cisco RP-B Route Processor and replace it with the Cisco CRS-PRP Route Processor.

Step 3 Reattach the Control Ethernet cables to the newly installed Cisco CRS-PRP Route Processor.

After you connect the cable, the newly installed Cisco CRS-PRP Route Processor synchronizes the Cisco IOS XR software packages on the Cisco RP-A or RP-B Route Processor.

Next, the active Cisco RP-A or RP-B Route Processor synchronizes the configuration by copying it to the newly-installed Cisco CRS-PRP Route Processor.

a. Package synchronization begins. After the package synchronization completes successfully, the Cisco CRS-PRP Route Processor will self-reload from the boot device, as shown in this example:

Nov 05 01:58:56.556 : Install (Node Preparation):    Please wait...
Nov 05 01:58:56.610 : Install (Node Preparation):    Completed syncing: 
/disk0/instdb/aliases/hfr-mini-px-4.0.1.50I
Nov 05 01:58:56.860 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
Nov 05 01:59:15.429 : Install (Node Preparation): Operation completed successfully. 
This node will now reload from disk0:.
Nov 05 01:59:15.429 : Install (Node Preparation):    Please wait...
Node 0/RP1/CPU0: insthelper: self-reset to use new boot image ...
 
 
 
 

b. After the self-reload of the Cisco CRS-PRP Route Processor there will be a quick re-synchronization of all the packages and metadata as part of complete package synchronization operation.

c. The configuration sync is triggered immediately after the re-synchronization of the packages and metadata. However, the newly-installed Cisco CRS-PRP Route Processor will never enter Standby Ready state when paired with the Cisco RP-A or RP-B Route Processor. There will be messages on the Cisco CRS-PRP Route Processor console as shown in the following example:

Nov 05 02:01:53.969 : Install (Node Preparation):    Completed syncing: 
/disk0/instdb/aliases/hfr-mini-px-4.0.1.50I
Nov 05 02:01:53.969 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
Nov 05 02:02:04.442 : PRP upgrade syncing configuration from dSC:   Please wait ...
Nov 05 02:02:50.220 : PRP upgrade configure sync success, src: 
/net/node0_RP0_CPU0/disk0:/config/, dest: /net/node0_RP1_CPU0/disk0:/config/
 
 

The alpha display on the Cisco CRS-PRP Route Processor now displays the SYNC READY state. The one caveat is that you cannot synchronize the crypto keys from the Active Route Processor if, for instance, SSH is used. The Cisco RP-A or RP-B Route Processor also indicates the SYNC READY state of the Cisco CRS-PRP status. Confirm this status by executing the show hfr command.

RP/0/RP0/CPU0:dSC-RP-B(admin)#show hfr | inc 0/RP
0/RP0/CPU0    RP(Active)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0    RP(Standby)       N/A              SYNC-READY      PWR,NSHUT,MON
RP/0/RP0/CPU0:dSC-RP-B(admin)#
 
 

Step 4 Verify that the package and configuration synchronization is complete by observing the SYNC READY state indication on the alpha display on the Cisco CRS-PRP Route Processor.

Step 5 Remove the LC fiber cable.

Step 6 Eject and remove the Active Cisco RP-A or RP-B Route Processor completely.


Note You must ensure that the Active Cisco RP-A or RP-B Route Processor is removed completely immediately after the completion of the configuration synchronization and immediately after the LC fiber cable is removed. Otherwise the whole process from steps 3 to 5 must be repeated after waiting15 minutes once the configuration synchronization completes.


Step 7 Reinsert the Cisco CRS-PRP Route Processor. This will cause a reload of the entire system. Since there is only one Route Processor in the system, the newly installed Cisco CRS-PRP Route Processor will become the Active Route Processor.

Step 8 After the reload completes and the Cisco CRS-PRP Route Processor has become the Active Route Processor, insert the second (Standby) Cisco CRS-PRP Route Processor. This will start the software package synchronization, followed by the self-reload and configuration synchronization.

Nov 09 01:25:22.797 : Install (Node Preparation): Completed sync of all packages and 
meta-data.
RP/0/RP0/CPU0:Nov  9 01:25:33.237: syslogd_helper: [92]: dsc_event_handler: Got SysMgr dSC 
event : 16
RP/0/RP0/CPU0:Nov  9 01:25:33.237: syslogd_helper: [92]: dsc_event_handler: syslogd_helper 
already received non DSC event 16
 
 

Step 9 The Standby Cisco CRS-PRP Route Processor now comes up in Standby Ready state. You can confirm this when the following syslog message displays:

RP/0/RP1/CPU0:Nov  4 08:13:03.505 : redcon[308]: %HA-REDCON-1-STANDBY_READY : standby card 
is ready 
 
 

Step 10 Verify that the Standby Cisco CRS-PRP Route Processor has attained NSR Ready State by executing the show redundancy summary command:

RP/0/RP0/CPU0:router# show redundancy summary
  
  Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
 
 

When the Standby Cisco CRS-PRP Route Processor is in NSR Ready State, the system is fully up and fully redundant. Now both Cisco RP-A or RP-B Route Processors can be replaced with Cisco CRS-PRP Route Processors on each of the remaining nDSC racks.

Step 11 On each of the remaining nDSC chassis, replace each Cisco RP-A or RP-B Route Processor with Cisco CRS-PRP Route Processors. The Cisco CRS-PRP Route Processor on the nDSC will synchronize the software and configuration from the DSC. All nDSC Line Card Chassis (LCCs) can be upgraded at the same time.

Step 12 If the newly-inserted Cisco CRS-PRP Route Processors on each of the remaining nDSC chassis do not start booting enter ROMMON and execute the following three commands listed below to modify the Config-register setting:

rommon1>confreg 0x102
rommon1>sync
rommon1>reset
 
 

The Standby Cisco CRS-PRP Route Processor now comes up in Standby Ready state. You can confirm this when the following syslog message displays:

RP/0/RP1/CPU0:Nov 4 08:13:03.505 : redcon[308]: %HA-REDCON-1-STANDBY_READY : standby card 
is ready 
 
 

Step 13 Verify that the Standby Cisco CRS-PRP Route Processor has attained NSR Ready State by executing the show redundancy summary command:

RP/0/RP0/CPU0:router# show redundancy summary
  
  Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
 
 

When the Standby Cisco CRS-PRP Route Processor is in NSR Ready State, the system is fully up and fully redundant. Now both the Cisco RP-A or RP-B Route Processors can be replaced with Cisco CRS-PRP Route Processors on each of the nDSC racks.

Step 14 When all the nDSC racks display "Standby Ready" for all the Standby Cisco CRS-PRP Route Processors and all the Standby Cisco CRS-PRP Route Processors are also in NSR Ready State, the system is fully up and fully redundant.


Method 1 - Caveats

There are few caveats with the Method 1 - Configuration & Package Synchronization Method, and they are listed below.

The user created directories will not be synchronized or copied.

The user fault management (EEM) scripts will not be copied.

The crypto Keys will not be copied.

In each case the workaround is to copy the directories, scripts, and/or crypto Keys manually.

Method 2 - Turboboot of the Cisco CRS-PRP Route Processor

This method involves turboboot of the Cisco CRS-PRP Route Processor. Use this method for a new deployment of Cisco CRS routers. You can also use it to pre-configure the Cisco CRS-PRP Route Processor with the Cisco IOS XR software Release 4.0.2 image in preparation for following the steps in "Method 3 - Routing Processor Swap Method".

Method 2 - Single Chassis Prerequisites

Turboboot requires a minimal ROMMON version of 2.03 at ROMMON A and B. This shouldn't be a concern for a new installation of Cisco CRS-PRP Route Processors in a new deployment of Cisco CRS routers, because they are shipped with ROMMON version of 2.03 or higher.

The target IOS-XR image (Cisco IOS XR software Release 4.0.2) must be available in disk2 (disk2 here is an USB disk). TFTP can also be used.

The running configuration should be backed up. It can be saved on a TFTP server.

Method 2 - Single Chassis Cisco CRS-PRP Route Processor Turboboot Procedure


Step 1 Connect Management and console cables to both Route Processor console ports and bring both Route Processors into ROMMON.

For more instructions, refer to the instructions in the Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers appendix of the Cisco IOS XR ROM Monitor Configuration Guide for the Cisco CRS Router online.

Step 2 Reset the config-register by setting it to 0x0 and then reload each Route Processor by executing the following ROMMON commands:

RP/0/RP0/CPU0:CRS-1(admin)#config-register 0x0
Tue Oct 12 06:11:29.712 PST
Successfully set config-register to 0x0 on node 0/RP0/CPU0
Successfully set config-register to 0x0 on node 0/RP1/CPU0
RP/0/RP0/CPU0:CRS-1(admin)#reload location all
 
 

When the system comes back up, take note of the ROMMON version in the pre-loading information. The version number displayed should reflect the new updated ROMMON version. See the following example:

Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
 
 
Initializing NVRAM...
Testing a portion of DDR SDRAM ...done
Reading ID EEPROMs ...
..........................Initializing SQUID ...
Initializing PCI ...
 
 
PCI0 device[1]: Vendor ID 0x10ee
PCI0 device[1]: Device ID 0x300e
PCI1 device[1]: Device ID 0xac55
PCI1 device[1]: Vendor ID 0x104c
PCI1 device[2]: Device ID 0x680
PCI1 device[2]: Vendor ID 0x1095
PCI1 device[3]: Device ID 0x5618
PCI1 device[3]: Vendor ID 0x14e4
PCI1 device[4]: Device ID 0x5618
PCI1 device[4]: Vendor ID 0x14e4
Configuring MPPs ...
Configuring PCMCIA slots ...
 
 
System Bootstrap, Version 2.1(20100723:223432) [CRS-1 ROMMON], 
Copyright (c) 1994-2010 by Cisco Systems, Inc.
Board type is 0x100006 (1048582)
 
 
Switch 0 initialized
Switch 1 initialized
Switch 0 Port fe0: link up (100Mb Full Duplex Copper)
Switch 0 Port ge0: link up (1000Mb Full Duplex Fiber)
Switch 0 Port ge1: link up (1000Mb Full Duplex Fiber)
Switch 1 Port ge1: link up (1000Mb Full Duplex Fiber)
GE0 port Up... Enabling
Enabling watchdog
G4(7457-SMP-MV64360 Rev 4) platform with 4096 MB of main memory
 
 
rommon B1 > 
 
 

Step 3 Configure the ROMMON variables on the standby Route Processor and reset by executing the following four ROMMON commands:

Rommon1>unset BOOT
Rommon2>confreg 0x102
Rommon3>sync
Rommon4>reset
 
 
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
 
 
Initializing NVRAM...
Testing a portion of DDR SDRAM ...done
Reading ID EEPROMs ...
..........................Initializing SQUID ...
Initializing PCI ...
 
 
PCI0 device[1]: Vendor ID 0x10ee
PCI0 device[1]: Device ID 0x300e
PCI1 device[1]: Device ID 0xac55
PCI1 device[1]: Vendor ID 0x104c
PCI1 device[2]: Device ID 0x680
PCI1 device[2]: Vendor ID 0x1095
PCI1 device[3]: Device ID 0x5618
PCI1 device[3]: Vendor ID 0x14e4
PCI1 device[4]: Device ID 0x5618
PCI1 device[4]: Vendor ID 0x14e4
Configuring MPPs ...
Configuring PCMCIA slots ...
System Bootstrap, Version 2.1(20100723:223432) [CRS-1 ROMMON], 
Copyright (c) 1994-2010 by Cisco Systems, Inc.
Board type is 0x100006 (1048582)
Switch 0 initialized
Switch 1 initialized
Switch 0 Port fe0: link up (100Mb Full Duplex Copper)
Switch 0 Port ge0: link up (1000Mb Full Duplex Fiber)
Switch 0 Port ge1: link up (1000Mb Full Duplex Fiber)
Switch 1 Port ge1: link up (1000Mb Full Duplex Fiber)
GE0 port Up... Enabling
Enabling watchdog
G4(7457-SMP-MV64360 Rev 4) platform with 4096 MB of main memory
 
 
rommon B1 > Socket = 0 Channel = 0 DIMM = 0 Rank = 35
Socket = 0 Channel = 1 DIMM = 0 Rank = 35
Socket = 0 Channel = 2 DIMM = 0 Rank = 35
 
 
J*n*T"Ntlhost board idprom: type=0x100009, pca version=0x2
KJF board idprom: 0x70012d
backplane nvram idprom i2c init not allowed on a SRP, or a bench setup
Satori board:0x100009 PCA Version:2, Revision:22
ZJF scratchpad_reg reset debug offset: 0x0,  total:5
    0 idx=0x0, addr=0xd5000000, val=0x7 - ZJF fpga_rev_reg
    1 idx=0x1, addr=0xd5000028, val=0x1 - ZJF reset_stat_reg
    2 idx=0x2, addr=0xd50000e8, val=0x0 - ZJF error_capture_reg
    3 idx=0x3, addr=0xd5000128, val=0x0 - ZJF prev_reset_stat1_reg
    4 idx=0x4, addr=0xd500012c, val=0x0 - ZJF prev_reset_stat2_reg
x86rmon_kensho_JF_P1_board_init
device B32:D0:F0 does not exist
device B32:D0:F0 10e78086 found
device B33:D0:F0 b33414e4 found
device B34:D0:F0 b33414e4 found
configure bcm unit:0 base addr:0xd0300000
configure bcm unit:1 base addr:0xd0400000
rommonSwitchInit(), init device 1 error rc=-9
rommonSwitchInit(), switching init device 1 error, rc=-9
S-16 P2 board CE port 29 workaround - probing 
rommonSwitchInit() unit:0, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit() unit:1, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit(): MDK initialization OK
BOOT-DEBUG init: finished mcp_nvraminit.
BOOT-INFO mem_init: confreg = 0x2.
                                  BOOT-DEBUG init: finished mem_init.
Image buffer base addr:0x65c3f010, image size:0x16800000
BOOT-DEBUG init: finished get_cpuid.
Total System RAM : 6144 MB
BOOT-INFO function emulate is at 0x7d37e959.
startable_processor_mask=0xf
Nirvana FPGA:
    rev_id: 0x2000b
    fw ready reg: 0x7ff0005
CPU chipset:
Jasper Forest: 1.0 
Ibex Peak    : 6 
Zen Japser Forest FPGA:
    rev_id: 0x7
    host_status_reg: 0x1
    reset_stat_reg: 0x1
    pch_status_reg: 0xf75
    pwr_status_reg: 0x0
    jf_stat_reg: 0x0
 
 
Current image running: Boot ROMB
 
 
System Bootstrap, Version 0.830 (Mon 10/11/2010 11:19:19.13) [CRS x86 ROMMON]
Copyright (c) 1994-2010 by Cisco Systems, Inc.
 
 
Reading confreg 0x2
 
 

Executing these four commands will bring up the standby Route Processor in a booting loop. If you turboboot a multishelf system you need to perform Step 3 on all non-DSC Route Processors. The Route Processor(s) will remain in the booting loop (MBI hunt) until they receive an MBI confirmation from the active Route Processor of the DSC that contains the remote image to boot from. The MBI confirmation will be received once the active Route Processor on the DSC has booted the mini image. Refer to  Step 4  on page -13.

Step 4 Configure the ROMMON variables on the active Route Processor and boot the vm image by executing the following ROMMON commands on the Active Route Processor:

Rommon1>IP_ADDRESS=<a.b.c.d>
Rommon2>IP_SUBNET_MASK=<mask>
Rommon3>TFTP_SERVER=<a.b.c.d>
Rommon4>DEFAULT_GATEWAY=<a.b.c.d>
Rommon5>unset BOOT
Rommon6>TURBOBOOT=on,disk0,format
Rommon7>sync
Rommon8>boot disk2:hfr-mini-px.vm-4.0.2
 
 

IMPORTANT: DO NOT use the option format with the TURBOBOOT variable if you migrate to a flash disk formatted with the FAT32 file system or if you have a flash disk formatted with FAT32.

In this case configure the TURBOBOOT variable as follows:

Rommon6>TURBOBOOT=on,disk0 
 
 

The example above reflects disk2: as the location for the vm image. To boot instead from the TFTP server, execute the command given below:

Rommon8>boot tftp://a.b.c.d/path/hfr-mini-px.vm-4.0.2
 
 

Step 5 Verify that the installation is complete by confirming that all nodes on the system are in state IOS XR RUN by executing the show platform command:

RP/0/RP0/CPU0:ios(admin)#show platform
Fri Feb 18 22:03:12.844 UTC
Node          Type              PLIM             State           Config State
------------- ----------------- ---------------- --------------- ---------------
0/0/SP        MSC(SP)           N/A              IOS XR RUN      PWR,NSHUT,MON
0/0/CPU0      MSC               Jacket Card      IOS XR RUN      PWR,NSHUT,MON
0/0/1         MSC(SPA)          4XOC48-POS       OK              PWR,NSHUT,MON
0/0/3         MSC(SPA)          8X1GE            OK              PWR,NSHUT,MON
0/0/5         MSC(SPA)          8X1GE            OK              PWR,NSHUT,MON
0/RP0/CPU0    RP(Active)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
 
 
 
 

Step 6 Configure the ROMMON variables on the standby Route Processor and reset by executing the following four ROMMON commands:

Rommon1>unset BOOT
Rommon2>confreg 0x102
Rommon3>sync
Rommon4>reset
 
 
Initializing DDR SDRAM...found 4096 MB
Initializing ECC on bank 0
Initializing ECC on bank 1
Initializing ECC on bank 2
Initializing ECC on bank 3
Turning off data cache, using DDR for first time
 
 
Initializing NVRAM...
Testing a portion of DDR SDRAM ...done
Reading ID EEPROMs ...
..........................Initializing SQUID ...
Initializing PCI ...
 
 
PCI0 device[1]: Vendor ID 0x10ee
PCI0 device[1]: Device ID 0x300e
PCI1 device[1]: Device ID 0xac55
PCI1 device[1]: Vendor ID 0x104c
PCI1 device[2]: Device ID 0x680
PCI1 device[2]: Vendor ID 0x1095
PCI1 device[3]: Device ID 0x5618
PCI1 device[3]: Vendor ID 0x14e4
PCI1 device[4]: Device ID 0x5618
PCI1 device[4]: Vendor ID 0x14e4
Configuring MPPs ...
Configuring PCMCIA slots ...
System Bootstrap, Version 2.1(20100723:223432) [CRS-1 ROMMON], 
Copyright (c) 1994-2010 by Cisco Systems, Inc.
Board type is 0x100006 (1048582)
Switch 0 initialized
Switch 1 initialized
Switch 0 Port fe0: link up (100Mb Full Duplex Copper)
Switch 0 Port ge0: link up (1000Mb Full Duplex Fiber)
Switch 0 Port ge1: link up (1000Mb Full Duplex Fiber)
Switch 1 Port ge1: link up (1000Mb Full Duplex Fiber)
GE0 port Up... Enabling
Enabling watchdog
G4(7457-SMP-MV64360 Rev 4) platform with 4096 MB of main memory
 
 
rommon B1 > Socket = 0 Channel = 0 DIMM = 0 Rank = 35
Socket = 0 Channel = 1 DIMM = 0 Rank = 35
Socket = 0 Channel = 2 DIMM = 0 Rank = 35
 
 
J*n*T"Ntlhost board idprom: type=0x100009, pca version=0x2
KJF board idprom: 0x70012d
backplane nvram idprom i2c init not allowed on a SRP, or a bench setup
Satori board:0x100009 PCA Version:2, Revision:22
ZJF scratchpad_reg reset debug offset: 0x0,  total:5
    0 idx=0x0, addr=0xd5000000, val=0x7 - ZJF fpga_rev_reg
    1 idx=0x1, addr=0xd5000028, val=0x1 - ZJF reset_stat_reg
    2 idx=0x2, addr=0xd50000e8, val=0x0 - ZJF error_capture_reg
    3 idx=0x3, addr=0xd5000128, val=0x0 - ZJF prev_reset_stat1_reg
    4 idx=0x4, addr=0xd500012c, val=0x0 - ZJF prev_reset_stat2_reg
x86rmon_kensho_JF_P1_board_init
device B32:D0:F0 does not exist
device B32:D0:F0 10e78086 found
device B33:D0:F0 b33414e4 found
device B34:D0:F0 b33414e4 found
configure bcm unit:0 base addr:0xd0300000
configure bcm unit:1 base addr:0xd0400000
rommonSwitchInit(), init device 1 error rc=-9
rommonSwitchInit(), switching init device 1 error, rc=-9
S-16 P2 board CE port 29 workaround - probing 
rommonSwitchInit() unit:0, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit() unit:1, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit(): MDK initialization OK
BOOT-DEBUG init: finished mcp_nvraminit.
BOOT-INFO mem_init: confreg = 0x2.
                                  BOOT-DEBUG init: finished mem_init.
Image buffer base addr:0x65c3f010, image size:0x16800000
BOOT-DEBUG init: finished get_cpuid.
Total System RAM : 6144 MB
BOOT-INFO function emulate is at 0x7d37e959.
startable_processor_mask=0xf
Nirvana FPGA:
    rev_id: 0x2000b
    fw ready reg: 0x7ff0005
CPU chipset:
Jasper Forest: 1.0 
Ibex Peak    : 6 
Zen Japser Forest FPGA:
    rev_id: 0x7
    host_status_reg: 0x1
    reset_stat_reg: 0x1
    pch_status_reg: 0xf75
    pwr_status_reg: 0x0
    jf_stat_reg: 0x0
 
 
Current image running: Boot ROMB
 
 
System Bootstrap, Version 0.830 (Mon 10/11/2010 11:19:19.13) [CRS x86 ROMMON]
Copyright (c) 1994-2010 by Cisco Systems, Inc.
 
 
Reading confreg 0x2
 
 

Executing these four commands will bring up the standby Route Processor in a booting loop. If you turboboot a multishelf system you need to perform Step 3 on all non-DSC Route Processors. The Route Processor(s) will remain in the booting loop (MBI hunt) until they receive an MBI confirmation with the remote image to boot from the active Route Processor of the DSC. The MBI confirmation will be received once the active Route Processor on the DSC has booted the mini image. Refer to the next step.

Step 7 Verify that the installation is complete by confirming that the Standby Cisco CRS-PRP Route Processors have attained NSR Ready State by executing the show redundancy summary command:

RP/0/RP0/CPU0:router# show redundancy summary
  
  Active Node    Standby Node
  ----------    ------------
  0/4/CPU0             N/A
  0/4/CPU1             N/A
  0/RP0/CPU0      0/RP1/CPU0 (Ready, NSR: Ready)
Reload and boot info  
--------------------- 
 
 
RP reloaded Wed Oct 13 09:23:20 2010: 10 minutes ago  
Active node booted Wed Oct 13 09:23:20 2010: 10 minutes ago  
Standby node boot Wed Oct 13 09:24:00 2010: 9 minutes ago  
Standby node last went not ready Wed Oct 13 09:33:14 2010: 29 seconds ago 
Standby node last went ready Wed Oct 13 09:33:15 2010: 28 seconds ago 
There have been 0 switch-¦-overs since reload  
Active node reload "Cause: Turboboot completed successfully"  
Standby node reload "Cause: MBI-¦-HELLO reloading node on receiving reload notification" 
 
 

Step 8 When the Standby Cisco CRS-PRP Route Processors are in NSR Ready State, the system is fully up and fully redundant.


Note For a more in-depth description of the turbo boot process, refer to the instructions in the Turbo Boot Procedure appendix of the Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide online.



Method 3 - Routing Processor Swap Method

This method involves swapping each legacy Cisco RP-B Route Processor with a Cisco CRS-PRP Route Processor during a maintenance window. The advantage of this method compared to Method 1 is reduced downtime while migrating the system to the Cisco CRS-PRP Route Processor. The disadvantage is that the configurations must be restored on the system after the hardware migration is complete.

Method 3 - Single Chassis Prerequisites:

Each Cisco CRS-PRP Route Processor must be running Cisco IOS XR software Release 4.0.2.

At least one Cisco CRS-PRP Route Processor must have the Cisco IOS XR software Release 4.0.2 image installed. Use either Method 1 or Method 2 to ensure that the Cisco CRS-PRP Route Processor has the Cisco IOS XR software Release 4.0.2 image installed.

The ROMMON version on the Cisco CRS-PRP Route Processor must match the ROMMON version released with Cisco IOS XR software Release 4.0.2. Both Cisco CRS-PRP Route Processors need to have the same ROMMON version. Refer to  Step 17  on page -19 for the procedure to upgrade the ROMMON using the FPD PIE.

The Running Configuration must be available on USB or available via TFTP.

Method 3 - Single Chassis Procedure:

The steps in this section provide the procedure to upgrade ROMMON on a single chassis Cisco CRS router, using the binary upgrade method.


Step 1 Download the tar file (rom2.03.tar from the targeted image package), un-tar it on a PC and copy the binaries to disk1: (assuming disk1 is the install disk)

These files should be on the flash disk (only the ppc files are required):

rommon-¦-hfr-¦-ppc7450-¦-sc-¦-dsmp-¦-A.bin 
rommon-¦-hfr-¦-ppc7450-¦-sc-¦-dsmp-¦-B.bin 
rommon-¦-hfr-¦-ppc7455-¦-asmp-¦-A.bin 
rommon-¦-hfr-¦-ppc7455-¦-asmp-¦-B.bin 
rommon-¦-hfr-¦-ppc8255-¦-sp-¦-A.bin 
rommon-¦-hfr-¦-ppc8255-¦-sp-¦-B.bin 
rommon-¦-hfr-¦-ppc8347-¦-sp-¦-A.bin 
rommon-¦-hfr-¦-ppc8347-¦-sp-¦-B.bin 
 
 

Step 2 Upgrade ROMMON B while in admin mode by executing the upgrade rommon b all disk1 command as shown in the following example:

RP/0/RP0/CPU0:CRS-C#admin  
Thu Jan 21 14:47:53.694 PST  
RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon b all disk1  
Thu Feb 16 14:49:16.608 PST  
Please do not power cycle, reload the router or reset any nodes until all upgrades are  
completed.  
Please check the syslog to make sure that all nodes are upgraded successfully. If you  
need to perform multiple upgrades, please wait for current  
 13 upgrade to be completed before proceeding to another upgrade. Failure to do so may  
render the cards under upgrade to be unusable.  
RP/0/RP0/CPU0:Feb 16 14:00:06.596 : upgrade_daemon[358]: Running rommon upgrade  
RP/0/RP1/CPU0:Feb 16 14:00:06.600 : upgrade_daemon[358]: Running rommon upgrade  
SP/0/SM3/SP:Feb 16 14:00:06.657 : upgrade_daemon[130]: Running rommon upgrade 
[SNIP] 
 
 

Step 3 Verify that ROMMON B was upgraded successfully by executing the show logging command.

RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully  
RP/0/RP0/CPU0:Feb 16 14:00:13.566 : rommon_burner[65770]: %PLATFORM-¦-  
ROMMON_BURNER-¦-5-¦-progress : ROMMON B is programmed successfully.  
RP/0/RP0/CPU0:Feb 16 14:00:13.523 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B  is 
programmed successfully.  
RP/0/RP0/CPU0:Feb 16 14:00:13.580 : syslog_dev[83]: upgrade_daemon[358]: OK, ROMMON B  is 
programmed successfully. 
[SNIP]  
 
 

Step 4 Now that ROMMON B is upgraded successfully, you can upgrade ROMMON A by executing the upgrade rommon a all disk1 command from admin mode as shown below:

RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk1 
 
 
Thu Feb 16 14:49:16.608 PST  
Please do not power cycle, reload the router or reset any nodes until all upgrades are  
completed.  
Please check the syslog to make sure that all nodes are upgraded successfully. If you  
need to perform multiple upgrades, please wait for current  
 13 upgrade to be completed before proceeding to another upgrade. Failure to do so may  
render the cards under upgrade to be unusable.  
RP/0/RP0/CPU0:Feb 16 14:00:06.596 : upgrade_daemon[358]: Running rommon upgrade  
RP/0/RP1/CPU0:Feb 16 14:00:06.600 : upgrade_daemon[358]: Running rommon upgrade  
SP/0/SM3/SP:Feb 16 14:00:06.657 : upgrade_daemon[130]: Running rommon upgrade 
[SNIP] 
 
 

Step 5 Verify that ROMMON A was upgraded successfully by executing the show logging command.

RP/0/RP0/CPU0:CRS-C(admin)#show logging | inc is programmed successfully
SP/0/3/SP:Feb 18 21:28:44.932 : rommon_burner[65562]: %PLATFORM-ROMMON_BURNER-5-progress : 
ROMMON A is programmed successfully.  
SP/0/3/SP:Feb 18 21:28:44.643 : syslog_dev[76]: upgrade_daemon[143]: OK, ROMMON A is 
programmed successfully.  
SP/0/2/SP:Feb 18 21:28:44.965 : rommon_burner[65562]: %PLATFORM-ROMMON_BURNER-5-progress : 
ROMMON A is programmed successfully.  
 
 

Step 6 Remove both the Standby and Active legacy Route Processors together.


Note As expected, removing both Route Processors will bring down the router.


Step 7 Connect Management and Console cables to the Cisco CRS-PRP Route Processor which will be inserted as the Active Route Processor.

Step 8 Insert the Cisco CRS-PRP Route Processor with Management and Console cables connected into Slot 0 of the Cisco CRS router.

Step 9 Wait till the newly-installed Cisco CRS-PRP Route Processor boots into XR_RUN state.

To verify that the newly-installed Cisco CRS-PRP Route Processor boots into XR_RUN state, execute the show platform command:

RP/0/RP0/CPU0:ios#show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
 
 

Step 10 Wait till the Cisco Fabric cards also attain XR_RUN state.

To verify that the Cisco Fabric cards also attain XR_RUN state, execute the show platform command in admin mode:

RP/0/RP0/CPU0:ios(admin)#show platform
Fri Feb 18 22:03:12.844 UTC
Node          Type              PLIM             State           Config State
------------- ----------------- ---------------- --------------- ---------------
0/0/SP        MSC(SP)           N/A              IOS XR RUN      PWR,NSHUT,MON
0/0/CPU0      MSC               Jacket Card      IOS XR RUN      PWR,NSHUT,MON
0/0/1         MSC(SPA)          4XOC48-POS       OK              PWR,NSHUT,MON
0/0/3         MSC(SPA)          8X1GE            OK              PWR,NSHUT,MON
0/0/5         MSC(SPA)          8X1GE            OK              PWR,NSHUT,MON
0/RP0/CPU0    RP(Active)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP      FC-40G/S(SP)      N/A              IOS XR RUN      PWR,NSHUT,MON
 
 
 
 

Step 11 Connect Management and Console cables to the Cisco CRS-PRP Route Processor which will be inserted as the Standby Route Processor.

Step 12 Insert the Cisco CRS-PRP Route Processor with Management and Console cables connected into the Cisco CRS router.

Step 13 Verify the synchronization between Standby and Active as shown below:

 
 
Cisco IOS XR Software for the Cisco XR HFR, Version 4.0.2.15I
Copyright (c) 2011 by Cisco Systems, Inc.
Path=0 - Intel PCH AHCI
 target=0 lun=0     Direct-Access(0) -          STEC MACH8 SSD   Rev: 0698
 target=1 lun=0     Direct-Access(0) -          STEC MACH8 SSD   Rev: 0698
SOC unit 0 attached to PCI device BCM56334_A0
Feb 18 22:32:44.303 : Install (Node Preparation): Install device root is /disk0/
Feb 18 22:32:44.305 : Install (Node Preparation): Trying device disk0:
Feb 18 22:32:46.220 : Install (Node Preparation): Checking size of device disk0:
Feb 18 22:32:46.221 : Install (Node Preparation):    OK
Feb 18 22:32:46.271 : Install (Node Preparation): Checking free space on disk0:
Feb 18 22:32:46.271 : Install (Node Preparation):    OK
Feb 18 22:32:46.272 : Install (Node Preparation): Starting package and meta-data sync
Feb 18 22:32:46.279 : Install (Node Preparation): Cleaning packages not in sync list
Feb 18 22:32:46.279 : Install (Node Preparation):    Please wait...
Feb 18 22:32:46.283 : Install (Node Preparation):    Complete
Feb 18 22:32:48.872 : Install (Node Preparation): Syncing package/meta-data contents: 
/disk0/instdb/ldpath 
Feb 18 22:32:48.872 : Install (Node Preparation):    Please wait...
Feb 18 22:32:48.911 : Install (Node Preparation):    Completed syncing: 
/disk0/instdb/ldpath
Feb 18 22:32:48.912 : Install (Node Preparation): Syncing package/meta-data contents: 
/disk0/instdb/ldpath.committed 
 
 

Step 14 Wait till the newly-installed Standby Cisco CRS-PRP Route Processor is NSR-ready. This is achieved after it boots into XR_RUN state.

To verify that the newly-installed Standby Cisco CRS-PRP Route Processor boots into XR_RUN state, execute the show platform command:

RP/0/RP0/CPU0:ios#show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
 

To verify that the newly-installed Standby Cisco CRS-PRP Route Processor is NSR ready, execute the show redundancy command:

RP/0/RP0/CPU0:router#show redundancy 
Wed Oct 13 09:33:43.367 UTC  
 
 
Redundancy information for node 0/RP0/CPU0:  
==========================================  
 
 
Node 0/RP0/CPU0 is in ACTIVE role  
Partner node (0/RP1/CPU0) is in STANDBY role  
Standby node in 0/RP1/CPU0 is ready  
Standby node in 0/RP1/CPU0 is NSR-¦-ready  
 
 
Reload and boot info  
--------------------- 
 
 
RP reloaded Wed Oct 13 09:23:20 2010: 10 minutes ago  
Active node booted Wed Oct 13 09:23:20 2010: 10 minutes ago  
Standby node boot Wed Oct 13 09:24:00 2010: 9 minutes ago  
Standby node last went not ready Wed Oct 13 09:33:14 2010: 29 seconds ago 
Standby node last went ready Wed Oct 13 09:33:15 2010: 28 seconds ago 
There have been 0 switch-¦-overs since reload  
Active node reload "Cause: Turboboot completed successfully"  
Standby node reload "Cause: MBI-¦-HELLO reloading node on receiving reload notification" 
 
 

Step 15 Insert the USB disk into the USB port on the Active Cisco CRS-PRP Route Processor.

Step 16 Copy the saved configuration from the USB disk to the running configuration using the copy disk2:<Saved_config_file_name> running-config command shown below and wait till the configuration is committed to running-configuration:

RP/0/RP0/CPU0:ios#copy disk2:<Saved_config_file_name> running-config 
Fri Feb 18 22:04:59.898 UTC
Parsing........
1813080 bytes parsed in 8 sec (226210)bytes/sec
Committing.
Prepared commit in 0 sec
 
 

Note The saved configuration can also be restored from a TFTP server.


Step 17 The next steps describe how to upgrade the Cisco CRS chassis by upgrading the FPD package installation envelope (PIE). You upgrade the FPD PIE by executing the upgrade hw-module fpd all location all command:

RP/0/RP0/CPU0:ios(admin)#upgrade hw-module fpd all location all
Fri Feb 18 20:49:31.996 UTC
 
 
% RELOAD REMINDER:  - The upgrade operation of the target module will not interrupt its 
normal
    operation. However, for the changes to take effect, the target module
    will need to be manually reloaded after the upgrade operation. This can
    be accomplished with the use of "hw-module <target> reload" command.
  - The output of "show hw-module fpd location" command will not display
    correct version information after the upgrade if the target module is
    not reloaded.
NOTE: Chassis CLI will not be accessible while upgrade is in progress.
Continue? [confirm]
This can take some time for a full chassis.
Ensure that system is not power cycled during the upgrades.
Please consult the documentation for more information.
Continue ? [no]: y
RP/0/RP0/CPU0:Feb 18 20:49:40.908 : upgrade_fpd_cli[65765]: %PLATFORM-UPGRADE_FPD-6-STATUS 
: FPD upgrade started. 
 
 
RP/0/RP1/CPU0:Feb 18 20:49:46.435 : lc_fpd_upgrade[294]: %PLATFORM-UPGRADE_FPD-6-START : 
Starting to downgrade rommon subtype image from 2.03 to 1.54 for for this card  on 
location 0/RP1/CPU0 
RP/0/RP1/CPU0:Feb 18 20:49:46.471 : upgrade_daemon[443]: Start Upgrade...
RP/0/RP1/CPU0:Feb 18 20:49:46.477 : u
 
 
FPD upgrade has ended.
 
 

Step 18 Reload the Cisco CRS chassis by executing the reload location all command:

RP/0/RP0/CPU0:ios(admin)#reload location all
Fri Feb 18 20:51:28.802 UTC
 
 
Preparing system for backup. This may take a few minutes especially for large 
configurations.
Status report: node0_RP0_CPU0: START TO BACKUP 
Status report: node0_RP0_CPU0: BACKUP HAS COMPLETED SUCCESSFULLY 
[Done]
Proceed with reload? [confirm]
RP/0/RP1/CPU0:Feb 18 20:53:49.749 : hbagent[223]: %PLATFORM-HBAGENT-2-NODE_RELOAD : Reload 
notification received. Reloading in 5 secs 
 
 

Step 19 Wait till the newly-installed Cisco CRS-PRP Route Processor boots into XR_RUN state.

To verify that the newly-installed Cisco CRS-PRP Route Processor boots into XR_RUN state, execute the show platform command:

RP/0/RP0/CPU0:ios#show platform
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
0/RP0/CPU0      RP(Active)      N/A             IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Standby)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
 

Step 20 Verify that the Existing Field Programmable Devices (ROMMON & FPGA) have the correct versions, using the sh hw-module fpd location all command as shown below:

RP/0/RP0/CPU0:LC-SCL-R1(admin)#sh hw-module fpd location all
Fri Feb 18 20:51:18.092 UTC
 
 
===================================== ==========================================
                                      Existing Field Programmable Devices
                                      ==========================================
                                        HW                       Current SW Upg/
Location     Card Type                Version Type Subtype Inst   Version   Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/0/SP       40G-MSC                    0.6   lc   rommonA 0       2.03     Yes
                                              lc   rommon  0       2.03     Yes
--------------------------------------------------------------------------------
0/0/CPU0     CRS1-SIP-800               0.112 lc   fpga1   0       6.00     Yes 
                                              lc   rommonA 0       2.03     Yes
                                              lc   rommon  0       2.03     Yes
--------------------------------------------------------------------------------
0/0/1        SPA-4XOC48POS/RPR          1.0   spa  fpga1   1       1.00     Yes 
--------------------------------------------------------------------------------
0/0/3        SPA-8X1GE-V2               1.1   spa  fpga1   3       1.10     Yes 
--------------------------------------------------------------------------------
0/0/5        SPA-8X1GE                  2.2   spa  fpga1   5       1.08     Yes 
--------------------------------------------------------------------------------
0/2/SP       40G-MSC                    0.6   lc   rommonA 0       2.03     Yes
                                              lc   rommon  0       2.03     Yes
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        N/A   lc   rommonA 0       2.03     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        N/A   lc   rommon  1       2.03     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        7.0   lc   fpga1   2       7.00     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        N/A   lc   fpga2   3       0.01     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                       13.0   lc   fpga3   4      13.00     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        N/A   lc   fpga4   5       0.01     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        N/A   lc   fpga5   6       0.01     Yes 
--------------------------------------------------------------------------------
0/RP0/CPU0   PRP                        2.0   lc   fpga6   7       2.00     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        N/A   lc   rommonA 0       2.03     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        N/A   lc   rommon  1       2.03     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        7.0   lc   fpga1   2       7.00     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        N/A   lc   fpga2   3       0.01     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                       13.0   lc   fpga3   4      13.00     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        N/A   lc   fpga4   5       0.01     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        N/A   lc   fpga5   6       0.01     Yes 
--------------------------------------------------------------------------------
0/RP1/CPU0   PRP                        2.0   lc   fpga6   7       2.00     Yes 
-------------------------------------------------------------------------------
 
 
 
 

Backout Procedure

The downgrade from Cisco CRS-PRP Route Processors back to Cisco RP-B or RP-A Route Processors using install commands is NOT supported.

In the event of a failure while upgrading to Cisco CRS-PRP Route Processors, the backout procedure is as follows:


Step 1 Enter each of the Cisco CRS-PRP Route Processors into ROMMON by executing the following commands:

RP/1/RP0/CPU0:CRS-1(admin)#config-register 0x0 loc all
 
 
Successfully set config-register to 0x0 on node 1/RP0/CPU0
Successfully set config-register to 0x0 on node 1/RP1/CPU0
 
 
RP/1/RP0/CPU0:CRS-1(admin)#reload loc all 
 
 

For more instructions on entering ROMMON, refer to the Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers appendix of the Cisco IOS XR ROM Monitor Configuration Guide for the Cisco CRS Router online.


Note On a multishelf system, perform this step on all DSC and nDSC nodes.


Step 2 Remove each of the Cisco CRS-PRP Route Processors from the Cisco CRS router.

Step 3 Put the old Cisco RP-B or RP-A Route Processors back into the Cisco CRS router. The old Cisco RP-B or RP-A Route Processors will start booting.

Step 4 Boot up each of the old Cisco RP-B or RP-A Route Processors (On a multishelf node, bring up Rack 0 first).

Step 5 On a multishelf node, insert the remaining old Cisco RP-B or RP-A Route Processors in the nDSC chassis. If the newly-inserted Cisco RP-B or RP-A Route Processors do not start booting enter ROMMON and execute the following three commands listed below to modify the Config-register setting:

rommon1>confreg 0x102
rommon1>sync
rommon1>reset