Cisco CRS-1 - Carrier Routing System Router User manual

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]
Cisco CRS-1 Carrier Routing System to
Cisco CRS-3 Carrier Routing System
Migration Guide
Cisco IOS XR Software Release 4.0
Text Part Number: OL-13669-03

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are
shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of
Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS,
Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing,
FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace,
MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath
are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between
Cisco and any other company. (1011R)
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
© 2011 Cisco Systems, Inc. All rights reserved.

iii
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
CONTENTS
Preface ix
Changes to This Document ix
Obtaining Documentation, Obtaining Support, and Security Guidelines ix
Migrating to a Cisco CRS-3 Carrier Routing System 1-1
Contents 1-1
CRS-1 to CRS-3 Software Migration Compatibility Matrix 1-2
Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing
System 1-3
ROMMON Upgrades 1-4
OPTION-A 1-4
OPTION-B 1-4
Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 1-5
Flash Disk Upgrade Process to 4GB 1-5
Inserting the 4GB Flashdisk 1-5
Disk Formatting 1-6
Verifying the Disk File System 1-6
Setting Up Disk Mirroring 1-6
Swapping Mirrored Disks 1-6
Verifying Standby RP Disk Upgrade 1-6
Performing Switchover 1-7
Upgrading the Standby RP 1-7
File System Upgrade Procedure for 2GB Flash Disks 1-7
Verifying that the System Meets RP Memory Requirements 1-9
IOS-XR Software Upgrade Procedure 1-9
Obtain the Required PIE Files 1-9
New Image Name Changes for 4.0 and Onwards 1-10
Verify System Stability 1-10
Additional Pre-upgrade System Checks 1-12
Upgrading toCisco IOS XR SoftwareRelease 4.0.X(PX) BeforeMigrating toCisco CRS-3Hardware 1-14
Post-Upgrade Procedure 1-16
Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility
Matrix 1-20

Contents
iv
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Information About Migrating to a Cisco CRS-3 Carrier Routing System 1-21
How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot) 1-23
Administratively Disabling the Fabric Plane 1-23
Disabling Power to the CRS-1 Fabric Card 1-25
Physically Removing the CRS-1 Fabric Card 1-27
Installing a CRS-3 Fabric Card 1-30
Verifying the Installation of the CRS-3 Fabric Card 1-35
Powering up the Replaced Fabric Card 1-37
How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot) 1-40
Administratively Disabling the Fabric Plane 1-40
Disabling Power to the CRS-1 Fabric Card 1-42
Physically Removing the CRS-1 Fabric Card 1-44
Installing a CRS-3 Fabric Card 1-47
Verifying the Installation of the CRS-3 Fabric Card 1-51
Powering up the Replaced Fabric Card 1-53
Booting Up the Newly Migrated Cisco CRS-3 Fabric 1-54
Administratively Enabling the Fabric Plane 1-54
Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node 1-55
Verifying Fabric Link Connectivity 1-56
How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot) 1-58
Administratively Disabling the Fabric Plane 1-59
Disabling Power to the CRS-1 Fabric Card 1-60
Physically Removing the CRS-1 Fabric Card 1-63
Installing a CRS-3 Fabric Card 1-65
Verifying the Installation of the CRS-3 Fabric Card 1-71
Powering up the Replaced Fabric Card 1-73
Booting Up the Newly Migrated Cisco CRS-3 Fabric 1-73
Administratively Enabling the Fabric Plane 1-74
Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node 1-74
Verifying Fabric Link Connectivity 1-75
Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System 1-80
Displaying Chassis Serial Numbers: Example 1-80
Adding a Fabric Card Chassis: Example 1-81
Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example 1-83
Where to Go Next 1-85
Additional References 1-86
Related Documents 1-86

Contents
v
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Technical Assistance 1-87
Downgrading Your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1 Carrier
Routing System Router 2-1
Contents 2-1
Prerequisites for Downgrading your Cisco CRS-3 Carrier Routing System Router Back to a Cisco CRS-1
Carrier Routing System Router 2-2
Contents 2-2
RestrictionsforDowngradingaCisco CRS-3CarrierRoutingSystemBacktoaCiscoCRS-1CarrierRouting
System Router 2-2
Downgrading your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis Back to a Cisco CRS-1
Carrier Routing System 16-Slot Line Card Chassis 2-2
Verifying the Fabric Plane Status 2-3
Administratively Disabling the Fabric Plane 2-5
Power Disable the Cisco CRS-3 Fabric Card 2-5
Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 Fabric 2-6
Physically Removing the Cisco CRS-3 Fabric Card 2-6
Installing a CRS-1 Fabric Card 2-9
Verifying the Installation of the CRS-1 Fabric Card 2-13
Powering up the Replaced Fabric Card 2-14
Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-17
Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-17
Administratively Enabling the Fabric Plane 2-18
Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 Node 2-18
Verifying Fabric Link Connectivity 2-19
Downgrading the Next Legacy Node 2-21
Downgrading your Cisco CRS-3 Carrier Routing System 8-Slot Line Card Chassis Back to a Cisco CRS-1
Carrier Routing System 8-Slot Line Card Chassis 2-22
Verifying the Fabric Plane Status 2-22
Administratively Disabling the Fabric Plane 2-24
Power Disable the Fabric Card 2-24
Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 Fabric 2-25
Physically Removing the CRS-3 Fabric Card 2-25
Installing a CRS-1 Fabric Card 2-29
Verifying the Installation of the CRS-1 Fabric Card 2-32
Powering up the Replaced Fabric Card 2-33
Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-36
Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-36
4.1.Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-37

Contents
vi
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Administratively Enabling the Fabric Plane 2-37
Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 Node 2-38
Verifying Fabric Link Connectivity 2-39
Downgrading the Next Legacy Node 2-41
Downgrading your Cisco CRS-3 Carrier Routing System 4-Slot Line Card Chassis Back to a Cisco CRS-1
Carrier Routing System 4-Slot Line Card Chassis 2-41
Verifying the Fabric Plane Status 2-42
Administratively Disabling the Fabric Plane 2-43
Power Disable the Fabric Card 2-44
Swap the Cisco CRS-3 Fabric with the Newly Installed Cisco CRS-1 Fabric 2-44
Physically Removing the CRS-3 Fabric Card 2-44
Installing a CRS-1 Fabric Card 2-49
Verifying the Installation of the CRS-1 Fabric Card 2-52
Powering up the Replaced Fabric Card 2-53
Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-56
Power-up the Newly Installed Cisco CRS-1 Fabric Card 2-57
Booting Up the Newly Downgraded Cisco CRS-1 Fabric 2-57
Administratively Enabling the Fabric Plane 2-57
Verifying Traffic Statistics on the Newly Downgraded Cisco CRS-1 Node 2-58
Verifying Fabric Link Connectivity 2-59
Downgrading the Next Legacy Node 2-61
Cisco CRS-3 Carrier Routing System Router Command Changes 3-1
New Commands 3-2
Modified Commands 3-27
Power Module Changes 3-71
List of QoS Changes for Cisco CRS Series Modular Services Card 140G (CRS-MSC-140G) Upgrade
Doc 3-73
Important Notes: QoS Configuration Changes 3-73
Modifying CRS-MSC-40G QoS Configurations for CRS-MSC-140G 3-73
QoS Command Changes 3-74
QoS Features Changes 3-76
General 3-76
Queueing 3-76
Policing 3-77

Contents
vii
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Turbo Boot Procedure A-1
Turbo Boot Prerequisites A-1
ROMMON Upgrade Instructions A-1
Turboboot Instructions A-2
Upgrading Your File System From FAT16 to FAT32 A-4
Cisco CRS-1 to Cisco CRS-3 Upgrade Decision Trees B-1
I NDEX

Contents
viii
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03

ix
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Preface
This guide describes how to upgrade a Cisco CRS-1 Carrier Routing System to a Cisco CRS-3 Carrier
Routing System. The second chapter describes how to downgrade your Cisco CRS-3 Carrier Routing
System back to a Cisco CRS-1 Carrier Routing System. Both chapters describe the upgrade or
downgrade process for each chassis type:
• 16-slot line card chassis
• 8-slot line card chassis
• 4-slot line card chassis
The preface contains the following sections:
• Changes to This Document, page ix
• Obtaining Documentation, Obtaining Support, and Security Guidelines, page ix
Changes to This Document
Table 1 lists the technical changes made to this document since it was first printed.
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Table 1 Changes to This Document
Revision Date Change Summary
OL-13669-01 October 2010 Initial release of the document.
OL-13669-02 December 2010 Adds 100GE support.
OL-13669-03 April 2011 Adds CRS-3 multishelf support.

Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
x
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03

CHAPTER
1-1
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
1
Migrating to a Cisco CRS-3 Carrier Routing
System
This chapter describes how to migrate a single-chassis Cisco CRS-1 Carrier Routing System to a
single-chassis Cisco CRS-3 Carrier Routing System.
Note For an introduction to the single-chassis Cisco CRS-3 Carrier Routing System, see Cisco CRS Carrier
Routing System 16-Slot Line Card Chassis System Description. For information on planning a
single-chassis Cisco CRS-3 Carrier Routing System system installation, see Cisco CRS Carrier Routing
System 16-Slot Line Card Chassis Site Planning Guide.
Feature History for the Cisco CRS-3 Carrier Routing System
Contents
This chapter contains the following sections:
• CRS-1 to CRS-3 Software Migration Compatibility Matrix, page 1-2
• Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing
System, page 1-3
• Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3, page 1-5
• File System Upgrade Procedure for 2GB Flash Disks, page 1-7
• IOS-XR Software Upgrade Procedure, page 1-9
• Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3
Hardware, page 1-14
Release Modification
Release 4.0.0.T The single-chassis Cisco CRS-3 Carrier Routing System was introduced.
Release 4.0.1 The single-chassis Cisco CRS-3 Carrier Routing System adds support for
100GE interfaces.
Release 4.0.2 Multishelf Cisco CRS-3 Carrier Routing System operation is supported and
multishelf Cisco CRS-1 Carrier Routing System to multishelf Cisco CRS-3
Carrier Routing System migration is supported.

1-2
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
CRS-1 to CRS-3 Software Migration Compatibility Matrix
• Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility
Matrix, page 1-20
• Information About Migrating to a Cisco CRS-3 Carrier Routing System, page 1-21
• How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot), page 1-23
• How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot), page 1-40
• How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot), page 1-58
• Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System, page 1-80
• Where to Go Next, page 1-85
• Additional References, page 1-86
Warning Do NOT insert any CRS-3 hardware before completing the software migration to Cisco IOS XR
software Release 4.0.0.T or higher.
CRS-1 to CRS-3 Software Migration Compatibility Matrix
Your existing Cisco CRS-1 16-Slot Line Card Chassis must be running 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) software before migrating to a Cisco CRS-3 16-Slot Line Card Chassis. Table 1-1 describes
the migration paths that are supported.
Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix
Current Version Migration Version DirectPIEUpgrade/Downgrade
Supported
3.4.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) No (must be done using Turbo Boot - refer to Appendix A for
more information)
3.5.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) No (must be done using Turbo Boot - refer to Appendix A for
more information)
3.6.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) No (must be done using Turbo Boot - refer to Appendix A for
more information)
3.7.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) No (must be done using Turbo Boot - refer to Appendix A for
more information)
3.8.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
3.8.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
3.8.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.

1-3
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System
Note All IOS-XR Software releases prior to 3.8.0 (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be upgraded
to IOS XR software release 3.8.0 or higher prior to being upgraded to IOS XR software release 44.0.0.T
(PX), 4.0.1(PX), or 4.0.2(PX) or be upgraded directly to IOS XR software release 4.0.0.T (PX),
4.0.1(PX), or 4.0.2(PX) using Turbo Boot - refer to Appendix A for more information.
PrerequisitesforUpgradingIOS-XRSoftwarePriortoMigrating
to a Cisco CRS-3 Carrier Routing System
Warning Do NOT insert any CRS-3 hardware before completing the software upgrade to Cisco IOS XR software
Release 4.0.0.T or higher.
3.8.3(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
Current Version Migration Version DirectPIEUpgrade/Downgrade
Supported
3.8.4(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
3.9.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
3.9.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
3.9.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) Yes. Migration to FAT32 recommended before
upgrading.
4.0.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) No (must be done using Turbo Boot - refer to Appendix A for
more information). Upgrade
package required.
4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) 4.0.0(PPC) No (downgrades must be done using Turbo Boot - refer to
Appendix A for more
information).
4.0.0.T (PX), 4.0.1(PX), or
4.0.2(PX) 3.x.x(PPC) No (downgrades must be done using Turbo Boot - refer to
Appendix A for more
information).
Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix (continued)

1-4
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System
At least a 2 GB FAT32 flashdisk is required to upgrade to Cisco IOS XR software Release 4.0.0.T (PX)
or Cisco IOS XR software Release 4.0.1(PX). Refer to the Cisco IOS-XR Flash Disk Requirements for
Migration to CRS-3 section for more information.
The minimum version of ROMMON software supported is ROMMON release 1.54. Refer to the
ROMMON Upgrades section for more information.
ROMMON Upgrades
Your existing Cisco CRS-1 16-Slot Line Card Chassis Route Processors (RPs) and Distributed Route
Processors (DRPs) must be running minimum ROMMON versions before migrating to a Cisco CRS-3
16-Slot Line Card Chassis. Table 1-2 describes the minimum ROMMON versions that are supported.
Warning While performing a turbo boot of 4.0.X (PX) images the ROMMON version needs to be 2.01 due to
image size increase, otherwise the turbo boot will fail. Refer to Appendix A for more information on
performing the turbo boot. Appendix A also describes how to upgrade your ROMMON version to 2.01
OPTION-A
Currently on most systems with IOS-XR Software Release 3.8.4 or higher or IOS-XR Software Release
3.9.0 or higher images ROMMON version 1.54 is supported/installed. While upgrading from IOS-XR
Software Release 3.8.4 or higher to IOS-XR Software Release 4.0.0.X (PX) you can upgrade the FPD
images using the Auto FPD procedure. The Auto FPD procedure upgrades the ROMMON images on
ROMMON B before resetting the router for upgrades. After the software upgrade is complete and the
router is up and running you then have to manually upgrade the ROMMON A images. Upgrade
ROMMON A by executing the following command from admin mode:
RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk0
For Auto FPD to work please execute the following command in admin mode
RP/0/RP0/CPU0:CRS-1(admin-config)# fpd auto-upgrade
OPTION-B
The other option is to upgrade the ROMMON manually after the image upgrade. The upgrade will not
fail even if the ROMMON images are 1.54 or 1.52.
Detailed procedures for ROMMON upgrade is detailed inthe 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.
Table 1-2 Cisco CRS-1 to Cisco CRS-3 IOS XR Software Supported ROMMON Versions
FPD Minimum Version Required
Route Processor (RP) 1.54
Distributed Route Processor (DRP) 1.54

1-5
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3
Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3
You can only upgrade your filesystem to FAT32 using the CLI specifed in this section if you are running
Cisco IOS XR software Release 3.8.2 or above.
If you are running a release of Cisco IOS XR software earlier than 3.8.2 please refer to Upgrading Your
File System From FAT16 to FAT32 in Appendix A, “Turbo Boot Procedure” for formatting the File
system to FAT32 using KSH.
Cisco IOS XR software Release 4.0.X (PX) requires at least a 2GB flash disk for installation or upgrade.
So prior to upgrading your current IOS XR software to IOS-XR Software Release 4.0.X (PX), you will
need to upgrade the flash disk to either 2GB or 4GB.
The size of the image is significantly higher on the Cisco CRS-3 because x86 support is now included
in addition to the PPC support. A FAT32 formatted flash disk will decrease the required space for the
file system significantly. It is highly recommended to use a 4G flash disk with FAT-32 file-system on the
Cisco CRS-3.
Checking your Existing Flash Disk Size
Execute the show filesystem command to check the actual disk0 size:
RP/0/RP0/CPU0:Router#sho filesystem
Wed Feb 11 15:28:57.401 PST PST
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - network rw qsm/dev/fs/tftp:
- - network rw qsm/dev/fs/rcp:
- - network rw qsm/dev/fs/ftp:
1043456 1005568 dumper-lnk rw qsm/dumper_nvram:
39929724928 39605428224 dumper-lnk rw qsm/dumper_harddisk:
1004994560 184500224 dumper-lnk rw qsm/dumper_disk1:
1024606208 423608320 dumper-lnk rw qsm/dumper_disk0:
62390272 49101348 dumper-lnk rw qsm/dumper_bootflash:
39929724928 39605428224 harddisk rw harddisk:
1024606208 423608320 flash-disk rw disk0:-----
1004994560 184500224 flash-disk rw disk1:
1043456 1005568 nvram rw nvram:
62390272 49101348 flash rw bootflash:
In the example shown, the flash disk (disk0) size is 1 Gig.
If the disk size is smaller than 2Gig you will need to upgrade the flash disk.
The procedures for flash disk upgrade are detailed in the Cisco XR 12000 Series Router and Cisco CRS-1
Router Flash Disk Upgrade Tasks document online here:
http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.html
Flash Disk Upgrade Process to 4GB
Inserting the 4GB Flashdisk
The first step is to insert a 4GB Cisco Authorized Flash disk into slot disk1 of Active and Standby RP.
After Insertion verify the 4GB disk is accessible from RP

1-6
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3
RP/0/RP0/CPU0:router# show filesystem disk1:
Model: UNIGEN FLASH
Capacity: 8215201 Sectors, Total 4206182912 Bytes, (512 Bytes/sector
Disk Formatting
Format the 4GB flashdisk on standby RP disk1: by executing the following command
RP/0/RP0/CPU0:ios#format disk1: partition filesystem fat32 location 0/rp1/cpu0
The above command will create a partition of 3.5/0.5 between disk1 and disk1a
Note Executing this command will not cause the RP to reset
Verifying the Disk File System
Verify the filesytem is changed to FAT32 file system and desired 80% and 20% partition between disk1
and disk1a disks by executing the following command
RP/0/RP0/CPU0:ios#show media location 0/rp1/cpu0
Mountpoint FsType FsType Size State DrvrPid Mirror Flags
================================================================================
/disk1: FAT16 FAT32 3.4G Mounted 0032792 Enabled
/disk1a: FAT16 FAT32 0.5G Mounted 0032792
Setting Up Disk Mirroring
Mirror the primary disk0 and standby disk1 disks on Standby RP using the command
RP/0/RP0/CPU0: LOAD(config)#mirror location 0/rp1/cpu0 disk0:disk1:
Verify that mirroring is enabled by executing the following command
RP/0/RP0/CPU0:LOAD#show mirror location 0/rp1/cpu0
Swapping Mirrored Disks
After verifying that disk mirroring is successfully enabled in the previous section, swap disk0 with disk1
(insert 4GB disk in disk0 slot)
Verifying Standby RP Disk Upgrade
Verify that the Standby RP boots with the 4GB flashdisk as the primary disk(disk0) on the Standby RP.

1-7
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System File System Upgrade Procedure for 2GB Flash Disks
Performing Switchover
Perform an RP switchover and verify that the Standby RP becomes the Active RP.
Upgrading the Standby RP
Once you have verified the switchover was successful, repeat the flashdisk upgrade steps on the new
Standby RP and verify results.
File System Upgrade Procedure for 2GB Flash Disks
First do the format of the boot device of the standby RP location.
format disk0: unpartition filesystem fat32 location 0/rp1/CPU0
This command formats the boot device of the standby RP and results in a reload of the standby RP. This
will result in a 2GB FAT32 file system, Since the device is unpartitioned means no disk mirroring.
Once the standby RP reload, it would come back, format the device with your specifications and would
start downloading all the packages from RP again. This takes time depending on the number of
packages/config you have on the RP.
Verify using the below command that Standby RP disk is running with your expected
filesystem/partition.
show media location 0/rp1/CPU0
Once the standby RP is up and running, perform a Switch Over from the active to the standby RP and let
the new Standby RP (old Active) come up as standby Ready.
Perform the process for the new standby RP location as well.
Reducing Disk Space Usage
If the flash disk size is 2 Gig you still may want to increase available disk space. In order to provide as
much room as possible on the disk, one can remove old files from the disk. This may include files which
the operator has placed on the disk device such as PIE files or temporary directories that have been
created.
When preparing for the upgrade to the next version of the operating system, the old, non-operational
version should be removed.
To remove old SMU files and old versions of the operating system use the admin-commands
install commit
to ensure all active packages are 'committed', then issue the command
install remove inactive
The install remove inactive test sync command can be used first to show which packages will be
removed from the disk.
Note In addition to checking the installation disk device, the bootflash device on the MSCs should also be
checked. Extraneous files such as crashinfo files can be removed.

1-8
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
File System Upgrade Procedure for 2GB Flash Disks
To check the free space of the bootflash use the following command:
dir bootflash: location 0/1/CPU0
Check if all the cards in the system are all up using the admin command
show platform
If any of the cards do not boot properly they have to be replaced or be shut down using the admin
command
hw-module power disable location <loc>
Minimizing Traffic Loss During the Upgrade
To minimize traffic loss during the upgrade please follow below steps:
Step 1 Make sure that all the traffic flowing through the router which needs to be upgraded has an alternate path.
In this scenario one can take one of the redundant routers out of service, upgrade it and then bring it back
into service without any significant traffic loss (this should work for the core routers, for the edge devices
usually the redundant path may not be available)
Step 2 Set IGP metric to the highest possible value so the IGP will try to route the traffic through the alternate
path.
For OSPF use the max-metric command.
router(config-ospf)#max-metric router-lsa
For ISIS use the spf-overload-bit command.
router(config-isis)#set-overload-bit
Step 3 After all the software is upgraded restore the IGP metric by removing the commands:
For OSPF use the no max-metric command
router(config-ospf)#no max-metric router-lsa
For ISIS use the no spf-overload-bit command.
router(config-isis)#no set-overload-bit
Prior to release 3.8 the above commands have to be run before the install activate command is executed,
resulting in a long period of time when the router is taken out of forwarding path.
To minimize this behavior starting from release 3.8, an enhancement has been provided which allows
you to pause the install activate command just prior to the router reloading and to execute configuration
changes such as IGP commands listed above.
Execute the following command to enable this install option:
router(config-isis)#install activate disk0:*4.0.* pause sw-change
You will be prompted prior to the system reload to execute configuration changes such as IGP
commands. At this point the IGP cost-out operation can be executed.
Step 4 Copy the running-configuration and admin-configuration to a temporary storage location. This could be
on a remote TFTP server or a device such as the hard disk: or disk0: present on the RP.
router#copy running-config tftp://…running_config.txt
router#admin
router(admin)#copy running-config tftp://…admin-running_config.txt
router(admin)#exit

1-9
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System IOS-XR Software Upgrade Procedure
Step 5 Verify Mgmt access to the router (see caveats section)
Step 6 While upgrading from 3.x.x images to 4.x.x images upgrade the file system of flash disks (boot device
which is typically disk0) to FAT32 file system for 2 GB and 4 GB flash disks. The procedure to upgrade
the file system of flash disks is different for 2GB and 4 GB Flash disks.
Verifying that the System Meets RP Memory Requirements
Due to image size increase on x86 based PX images you will need to have at least 1 GB of free memory
on each of the Route Processor (RP) modules.
Execute the following command to verify the free memory on the RP.
RP/0/RP0/CPU0:BELUGA-QQ-4#show memory
Tue Oct 12 22:17:28.761 PST
Physical Memory: 4096M total (1840M available)
IOS-XR Software Upgrade Procedure
For links to the latest IOS XR software upgrade instructions, refer to the Cisco IOS XR General
Information page here:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
Obtain the Required PIE Files
The Composite Mini Package is mandatory to perform the upgrade. The additional PIE files listed below
are optional. whether they are needed or not depends on your router configuration and required features:
Table 1-3 OS XR PPX Software PIE Filenames
PIE File Description Sample PIE Filename Package Name
Mini Package (OS-MBI, Base,
Admin, Fwdg, lc Rout) hfr-mini-px.pie-4.0.1 or 4.0.2 disk0:comp-hfr-mini-px-4.0.1 or 4.0.2
Upgrade Package*(see note) hfr-upgrade-px.pie-4.0.1 or
4.0.2 disk0:hfr-px-upgrade-4.0.1 or 4.0.2
Multicast Package hfr-mcast-px.pie-4.0.1 or
4.0.2 disk0:hfr-mcast-px-4.0.1 or 4.0.2
Manageability Package hfr-mgbl-px.pie-4.0.1 or
4.0.2 disk0:hfr-mgbl-px-4.0.1 or 4.0.2
MPLS Package hfr-mpls-px.pie-4.0.1 or
4.0.2 disk0:hfr-mpls-px-4.0.1 or 4.0.2
Security Package hfr-k9sec-px.pie-4.0.1 or
4.0.2 disk0:hfr-k9sec-px-4.0.1 or 4.0.2
Diagnostic package hfr-diags-px.pie-4.0.1 or
4.0.2 disk0:hfr-diags-px-4.0.1 or 4.0.2

1-10
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide OL-13669-03
Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System
IOS-XR Software Upgrade Procedure
Note The filenames listed here may not necessarily be the filenames of the actual files since the files can be
renamed. The actual filenames used will not affect the operation.
Note The upgrade Package needs to be activated along with the Mini Package.PIE file. The Upgrade Package
is ONLY mandatory when performing the upgrade from 3.x to 4.x. The upgrade package must be
deactivated and removed after the 3.x to 4.x upgrade operation is complete.
Currently removing the upgrade PIE file triggers a false error message stating that all the active
packages will be removed. This message is due to a known bug which will be fixed in later releases. You
can ignore this the false warning message and safely go ahead and remove the upgrade package despite
the false warning message.
New Image Name Changes for 4.0 and Onwards
Table 1-4 lists the new file names for the images for IOS XR Software release 4.0.1(PX) and onwards.
.-p – only ppc based images
.-px – ppc + x86 based images
Verify System Stability
The following commands should be executed to verify basic system stability before the upgrade:
Execute the show platform command while in admin mode to verify that all nodes are in "IOS XR
RUN" state, the PLIMs are in "OK" state, and that the SPAs are in "READY" state.
Documentation package hfr-doc-px.pie-4.0.1 or
4.0.2 disk0:hfr-doc-px-4.0.1 or 4.0.2
Field Programmable Device package hfr-fpd-px.pie-4.0.1 or
4.0.2 disk0:hfr-fpd-px-4.0.1 or 4.0.2
Table 1-3 OS XR PPX Software PIE Filenames (continued)
Table 1-4 New Image Name Changes for IOS XR Software Release 4.0.1 (PX) and Onwards
Old File Name New File Name Old Name on Router New Name on Router
comp-hfr-mini.vm hfr-mini-p.vm comp-hfr-mini-4.0.1 hfr-mini-p-4.0.1
comp-hfr-full.vm hfr-full-p.vm comp-hfr-full-4.0.1 hfr-full-p-4.0.1
comp-hfr-mini-px.vm hfr-mini-px.vm comp-hfr-mini-px-4.0.1 hfr-mini-px-4.0.1
comp-hfr-full-px.vm hfr-full-px.vm comp-hfr-full-px-4.0.0.17C hfr-full-px-4.0.1
comp-hfr-mini.pie hfr-mini-p.pie comp-hfr-mini-4.0.1 hfr-mini-p-4.0.1
comp-hfr-mini-px.pie hfr-mini-px.pie comp-hfr-mini-px-4.0.1 hfr-mini-px-4.0.1
hfr-fpd.pie hfr-fpd-p.pie hfr-fpd-4.0.1 hfr-fpd-p-4.0.1
hfr-upgrade.pie hfr-upgrade-p.pie NA NA