Cisco CRS-1 - Carrier Routing System Router, CRS-3 Migration Manual

Cisco CRS-1 Carrier Routing System to
Cisco CRS-3 Carrier Routing System
Migration Guide

Cisco IOS XR Software Release 4.0

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]

Text Part Number: OL-13669-03

THE SPECIFICATIONS AND INFORMATION RE GARDIN G THE PRODU CTS IN THIS MANU AL A RE SUBJ ECT TO CHANGE WITH OUT N OTICE. ALL ST ATEM ENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELI EVED TO BE ACCURA TE BUT ARE PRESENTE D WITHOUT WARRA NTY OF ANY KIND ,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBI LITY FOR TH EIR APPLICAT ION O F ANY PRO DUCTS.

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 prog r am devel oped by the U niver sit y of Cali forni a, Ber keley ( UCB) as p art of UCB’ s pub lic domain ver si on
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTH ER WARRANTY HER EIN, ALL DOCUMEN T FILES AND SOFTWA RE OF THESE SUPP LIERS ARE PROVID ED “AS IS” WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSE D OR
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRIN GEMENT OR A RISING FRO M A CO URSE OF DEAL ING, USA GE, OR T RADE
PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFIT S OR L OSS O R DA MAG E TO DA TA AR I SI NG O UT OF THE USE OR INABILITY TO US E T HI S MA NU AL , EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses us ed in this docum ent ar e not i ntend ed to be act ual ad dresses. Any exampl es, com mand displ ay 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/Sol ver, EtherChannel, EtherFast, Et herSwitch, Fast Step, Follow Me B rowsing,
FormShare, GigaDrive, HomeLink, Internet Quot ient, IOS, iPhon e, 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 Inter net Quotient, and Trans Path
are registered trademarks of Cisco

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. (1011 R)

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

© 2011 Cisco Systems, Inc. All rights reserved.

Systems, Inc. and/or its affiliates in the United States and certain other countries.

IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF

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 to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 1-14

Post-Upgrade Procedure 1-16

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility
Matrix

OL-13669-03

1-20

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

iii

Contents

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

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

iv

OL-13669-03

Contents

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
Restrictions for Downgrading a Cisco CRS-3 Carrier Routing System Back to a Cisco CRS-1 Carrier Routing

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

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

OL-13669-03

2-22

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

v

Contents

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

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

vi

OL-13669-03

I

NDEX

Contents

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

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

vii

Contents

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

viii

OL-13669-03

Preface

This guide describes how to upgrade a Cis co 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.

Tab le 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.

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

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

OL-13669-03

documents, see the monthly

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

ix

Obtaining Documentation, Obtaining Support, and Security Guidelines

Preface

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

x

OL-13669-03

CHAPTER

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

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
System 16-Slot Line Card Chassis Site Planning Guide.

Feature History for the Cisco CRS-3 Carrier Routing System

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

Release 4.0.2 Multishelf Cisco CRS-3 Carrier Routing System operation is supported and

CRS-3 Carrier Routing System.

CRS-3 Carrier Routing System system installation, see Cisco CRS Carrier Routing

100GE interfaces.

multishelf Cisco
Carrier Routing System migration is supported.

CRS-1 Carrier Routing System to multishelf Cisco CRS-3

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

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-1

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

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

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
the migration paths that are supported.

Tab le 1-1 CRS-1 to CRS-3 Softw are Migration Compatibility Matr ix

Current Version Migration Version

3.4.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.5.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.6.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.7.x(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.8.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.8.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.8.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

CRS-3 16-Slot Line Card Chassis. Table 1-1 describes

Direct PIE Upgrade/Downgrade
Supported

No (must be done using Turbo
Boot - refer to Appendix A for
more information)

No (must be done using Turbo
Boot - refer to Appendix A for
more information)

No (must be done using Turbo
Boot - refer to Appendix A for
more information)

No (must be done using Turbo
Boot - refer to Appendix A for
more information)

Yes. Migration to FAT32
recommended before
upgrading.

Yes. Migration to FAT32
recommended before
upgrading.

Yes. Migration to FAT32
recommended before
upgrading.

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-2

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

Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix (continu ed)

3.8.3(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

Current Version Migration Version

3.8.4(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.9.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.9.1(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

3.9.2(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

4.0.0(PPC) 4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

4.0.0.T (PX), 4.0.1(PX), or

4.0.2(PX)

4.0.0(PPC) No (downgrades must be done

3.x.x(PPC) No (downgrades must be done

Yes. Migration to FAT32
recommended before
upgrading.

Direct PIE Upgrade/Downgrade
Supported

Yes. Migration to FAT32
recommended before
upgrading.

Yes. Migration to FAT32
recommended before
upgrading.

Yes. Migration to FAT32
recommended before
upgrading.

Yes. Migration to FAT32
recommended before
upgrading.

No (must be done using Turbo
Boot - refer to Appendix A for
more information). Upgrade
package required.

using Turbo Boot - refer to
Appendix A for more
information).

using Turbo Boot - refer to
Appendix A for more
information).

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 softw are 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.

Prerequisites for Upgrading IOS-XR Software Prior to Migrating
to a Cisco

Warning

OL-13669-03

CRS-3 Carrier Routing System

Do NOT insert any CRS-3 hardware before completing the software upgrade to Cisco IOS XR software
Release 4.0.0.T or higher.

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-3

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 F AT32 flashdisk is required to upgrade to Cisco IOS XR software Release 4.0.0.T (PX)
or Cisco

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.

IOS XR software Release 4.0.1(PX). Refer to the Cisco IOS-XR Flash Disk Requirements for

ROMMON Upgrades

Your existing Cisco CRS-1 16-Slot Line Card Ch assis Route Proce ssors (RPs) an d Distributed Route
Processors (DRPs) must be running minimum ROMMON versions before migrating to a Cisco
16-Slot Line Card Chassis.

Tab le 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

Table 1-2 describes the minimum ROMMON versions that are supported.

CRS-3

Warning

OPTION-A

OPTION-B

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

Currently on most systems with IOS-XR Softw are Re lease 3.8.4 or hi gher or IOS-X R Softwa re 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

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.

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-4

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 u sing 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 int o slot disk1 of Act ive and Standby RP.
After Insertion verify the 4GB disk is accessible from RP

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-5

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

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

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 i n the previ ous section, swap disk0 w ith 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.

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-6

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 stan db y RP an d results i n a reload of t he 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 acti v e to the standb y 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 f iles from the disk. This may include f iles 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 re move in ac tive

The install re move i na ctive te st s yn c 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.

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-7

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 traff ic flowing through the router which needs to be upgraded h as an alternate path .

In this scenario one can take one of the redundant r outers out of service, upg rade it and then bring it back
into service without any significant t raffic loss (this sh ould work for the core routers, for the edge de vices
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.

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

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 in stall op tion:

router(config-isis)#install activate disk0:*4.0.* pause sw-change

You will be prompted pri or to the sy stem reload to execute configuration change s such as IGP
commands. At this point the IGP cost-out operation can be executed.

Step 4 Copy the running-configuration and admin-configur ation to a temporary sto rage location. This co uld 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

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-8

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

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 x8 6 bas ed PX i mag es 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

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 additio nal PIE files listed belo w
are optional. whether they are needed or not depends on your router configurati on and req uired features:

Tab le 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)

Upgrade Package* (see note) hfr-upgrade-px.pie-4.0.1 or

Multicast Package hfr-mcast-px.pie-4.0.1 or

Manageability Package hfr-mgbl-px.pie-4.0.1 or

MPLS Package hfr-mpls-px.pie-4.0.1 or

Security Package hfr-k9sec-px.pie-4.0.1 or

Diagnostic package hfr-diags-px.pie-4.0.1 or

hfr-mini-px.pie-4.0.1 or

4.0.2

4.0.2

4.0.2

4.0.2

4.0.2

4.0.2

4.0.2

disk0:comp-hfr-mini-px-4.0.1
or 4.0.2

disk0:hfr-px-upgrade-4.0.1 or

4.0.2
disk0:hfr-mcast-px-4.0.1 or

4.0.2
disk0:hfr-mgbl-px-4.0.1 or

4.0.2
disk0:hfr-mpls-px-4.0.1 or

4.0.2
disk0:hfr-k9sec-px-4.0.1 or

4.0.2
disk0:hfr-diags-px-4.0.1 or

4.0.2

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-9

IOS-XR Software Upgrade Procedure

Table 1-3 OS XR PPX Software PIE Filenames (continued)

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Documentation package hfr-doc-px.pie-4.0.1 or

4.0.2

Field Programmable Device package hfr-fpd-px.pie-4.0.1 or

4.0.2

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 kno wn bu g which will be f ix ed 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.

disk0:hfr-doc-px-4.0.1 or

4.0.2
disk0:hfr-fpd-px-4.0.1 or

4.0.2

Tab le 1-4 New Image Name Changes f o r 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

.-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.

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-10

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

RP/0/RP0/CPU0:router(admin)#show platform
Tue Oct 12 23:34:37.898 PST
Node Type PLIM State Config State

--------------------------------------------------------------------------------------

­0/0/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/1/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/2/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/3/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/4/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/5/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/6/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/7/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/8/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/9/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/10/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/11/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/12/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON
0/13/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON
0/14/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/14/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON
0/14/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON
0/15/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/15/CPU0 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON
0/15/CPU1 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON
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
0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON
0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON

IOS-XR Software Upgrade Procedure

OL-13669-03

Execute the show redundancy command to verify that a Standby RP is available and in "ready" state.

RP/0/RP0/CPU0:router#show red
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

Execute the show ipv4 interface brief command or the show ipv6 interface brief command or the show
interface summary command to verify that all necessary interfaces are "UP".

RP/0/RP0/CPU0:router#show interfaces summary
Tue Oct 12 23:41:48.562 PST
Interface Type Total UP Down Admin Down

-------------- ----- -- ---- ---------­ALL TYPES 750 712 0 38

--------------
IFT_LOOPBACK 1 1 0 0
IFT_ETHERNET 6 2 0 4
IFT_NULL 1 1 0 0
IFT_TENGETHERNET 232 198 0 34
IFT_VLAN_SUBIF 510 510 0 0

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-11

IOS-XR Software Upgrade Procedure

show install active summary (verify that the proper set of packages are active)
Single-chassis example:

RP/0/RP0/CPU0:router(admin)#show install active summary
Wed Oct 13 06:47:17.604 UTC
Default Profile:
Admin Resources
SDRs:
Owner
Active Packages:
disk0:hfr-cgn-px-4.0.0.65I
disk0:hfr-mpls-px-4.0.0.65I
disk0:hfr-mcast-px-4.0.0.65I
disk0:hfr-mini-px-4.0.0.65I

Multishelf example:

RP/0/RP0/CPU0:MC-SCALE(admin)#show install active summary
Default Profile:
Admin Resources
SDRs:
Owner
taiko-sdr
Active Packages:
disk0:hfr-fit-px-4.0.2.19I
disk0:hfr-doc-px-4.0.2.19I
disk0:hfr-mpls-px-4.0.2.19I
disk0:hfr-mgbl-px-4.0.2.19I
disk0:hfr-mcast-px-4.0.2.19I
disk0:hfr-mini-px-4.0.2.19I
disk0:hfr-fpd-px-4.0.2.19I
disk0:hfr-diags-px-4.0.2.19I

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Execute the cfs check/clear configuration inconsistency command to verify/fix configuration file
system in exec and admin mode.

Additional Pre-upgrade System Checks

Due to increasing size of the images sufficient disk space is required to perform the upgrade. the 2Gig
flash disk option was first introduced in release 3.7.0, An optional 4Gig flash disk is available starting
with the IOS XR 3.8.4 release.

When upgrading to release 4.0.0 or higher, a PCMCIA flash disk of 2Gig or lar ger has to be instal led in
the system BEFORE the software upgrade is performed.

Step 1 Use the show filesystem command to check the actual disk0 size:

RP/0/RP0/CPU0:router(admin)#show filesystem
Wed Oct 13 06:54:57.000 UTC
File Systems:

3694129152 1131577344 flash-disk rw disk0:
2102788096 2102657024 flash-disk rw disk1a:
2102722560 180682752 flash-disk rw disk1:
504471552 504152064 flash-disk rw disk0a:

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-12

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

1043456 940032 nvram rw nvram:
62390272 25756520 flash rw bootflash:

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, any old, non-operational
versions should be removed.

Step 2 Remove old SMUs and old versions of the operating system files by executing the following admin

commands:

RP/0/RP0/CPU0:router(admin)# show install inactive

Node 0/0/CPU0 [LC] [SDR: Owner]
Boot Device: mem:
Inactive Packages:
disk0:hfr-fit-px-4.0.0.63I
disk0:hfr-infra-test-px-4.0.0.65I
disk0:hfr-upgrade-px-4.0.0.65I
disk0:hfr-fit-px-4.0.0.65I
disk0:hfr-cgn-px-4.0.0.63I
disk0:hfr-mpls-px-4.0.0.63I
disk0:hfr-mcast-px-4.0.0.63I
disk0:hfr-fpd-px-4.0.0.65I
disk0:hfr-fpd-px-4.0.0.63I
disk0:hfr-diags-px-4.0.0.63I
disk0:hfr-diags-px-4.0.0.65I

Execute the install remove inactive test sync command first to show which packages will be removed
from the disk.

RP/0/RP0/CPU0:router(admin)#install remove inactive test sync
Info: This operation will remove the following packages:
Info: disk0:hfr-diags-px-4.0.0.65I
Info: disk0:hfr-diags-supp-4.0.0.65I
Info: disk0:hfr-doc-px-4.0.0.65I
Info: disk0:hfr-doc-supp-4.0.0.65I
Info: disk0:hfr-fit-px-4.0.0.65I
Info: disk0:hfr-fit-4.0.0.65I

IOS-XR Software Upgrade Procedure

The install operation will continue asynchronously.

RP/0/RP0/CPU0:router(admin)#Install operation 192 completed successfully

Step 3 Ensure all active packages are 'committed', then issue the install commit command

RP/0/RP0/CPU0:router(admin)#install commit
Wed Oct 13 07:10:37.141 UTC
Install operation 193 '(admin) install commit' started by user 'lab' via CLI at
07:10:38 UTC Wed Oct 13 2010.
Install operation 193 completed successfully at 07:10:46 UTC Wed Oct 13 2010.

If any node is not booting properly it has to be replaced or shut down using the hw-module power
disable location 0/1/cpu0 command executed while in admin mode

RP/0/RP0/CPU0:router(admin-config)#hw-module power disable location 0/1/cpu0

Step 4 Copy the running-configuration and admin-configur ation to a temporary sto rage location. This co uld be

on a remote TFTP server or a device such as the harddisk: or disk0: present on the RP.

router#copy running-config tftp://…running_config.txt
router#admin

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-13

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

router(admin)#copy running-config tftp://…admin-running_config.txt
router(admin)#exit

Step 5 Verify Mgmt access to the router

Note Cisco recommends copying all the Mandatory PIE files, Optional PIE files, and Recommended

SMUs to the hard disk as part of pre-maintenance acti vity. This will save significant time duri ng
the upgrade process.

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before
Migrating to Cisco

Before migrating your CRS-1 hardware to CRS-3 hardware you must complete the software upgrade to
Cisco

IOS XR software Release 4.0.X(PX).

Note All install operations should be done while logged into admin mode.

Step 1 Add the required PIEs to disk:

router(admin)# install add tar <source>/<path>/<pie> sync

The <source> keyword can be one of disk0:, disk1:, compactflash:, harddisk:, tftp:, ftp: or

.

rcp:

The above step must be repeated for each PIE file, or all of the PIEs can be added together in a single
install add command. To add all PIEs using a single command, list all of the PIEs (including their
source) within the install add command in the following manner:

router(admin)# install add <source>/hfr-mini-px.pie-<version>
<source>/hfr-mcast-px.pie-<version> <source>/hfr-mgbl-px.pie-<version>
<source>/hfr-mpls-px.pie-<version> <source>/hfr-k9sec-px.pie-<version>
<source>/hfr-diags-px.pie-<version> hfr-upgrade-px.pie sync

Note The use of the sync option prevents other users from executing any other command during the

install operation.

CRS-3 Hardware

The <source> keyword can be specified just once rather than for each package. This simplifies the
command:

router(admin)# install add <source> hfr-mini-px.pie-<version>
hfr-mcast-px.pie-<version> hfr-mgbl-px.pie-<version> hfr-mpls-px.pie-<version>
hfr-k9sec-px.pie-<version> hfr-diags-px.pie-<version> hfr-upgrade-px.pie <version>
sync

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-14

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Note Under idle conditions, the "install add" operation may take up to 65 to 100 minutes. During the

“install add” operation your Cisco CRS Series router will remain fully functional.

Note If you have any other optional packages installed, the current upgrade has to be done with the

optional packages already installed. Otherwise all optional packages have to be deactivated
(following by the commit) before the upgrade. Side effect of this is loss of the configuration
supported by the PIE.

From Cisco IOS XR software release 3.6.0 onward, an alternate way of adding and installing PIEs is
available. If the PIE files are compressed using tar format they can be loaded on the router using the
following command:

router(admin)# install add tar <source>/<path>/<tar_file> sync

Step 2 Test the activation using the test option. Testing the activation will give you a preview of the activation.

router(admin)# install activate disk0:hfr-mini-px.pie<version>
disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version>
disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version>
disk0:hfr-diags-px.pie<version> hfr-upgrade-px.pie sync test

Note No actual changes will be made when you use the test option with the sync command.

Any config that is incompatible with the new version being activated will be identified. The
show configuration removed command can be used to view what will be removed as resu lt of
the software upgrade (see the Caveats section for details).

Each removed configuration can be reapplied using the load config removed <config>.cfg
command from config mode AFTER the upgrade has been completed (see the Caveats section for
details).

From Cisco IOS XR software release 3.6 onwards, the install command will accept the use of
wildcard pattern matching. The install activate command can be simplified to install activate *3.9*
sync test.

FromCisco IOS XR software release 3.7.0 onwards, PIEs can subsequently be activated using the
following single command. Th e

<install_operation_id> variable is based on the install operation

ID generated after each install command:

router(admin)# install activate id <install_operation_id> sync test

The install operation ID is printed after finishing each install command or can be obtained by
running the show install log command.

Step 3 Activate all of the packages added in step 1:

router(admin)# install activate disk0:hfr-mini-px.pie<version>
disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version>
disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version>
disk0:hfr-diags-px.pie<version> hfr-upgrade-px.piesync

The output of the install add command executed in step 1 provides the list of names of packages to be
used in the install activate operation.

Using the sync option prevents other users from executing any other commands during the install
operation.

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-15

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

The router will reload at the end of activation to start using the new packages.

Note Under idle conditions, this operation may take at least 20 minutes to complete.

From Cisco IOS XR software release 3.8 onwards, the install command install activate *3.9.* pause
sw-change sync can be used to enable the user to cost the router out of th e IGP path just before the rout er

reloads, rather than at the point where the activation commences.

Step 4 Verify system stability through executing the commands described under the Check System Stability

section. This release does not support downgrades from PX to P images.

Step 5 Verify activation is successful. Once activation is done and before the install commit operation,

deactivate and remove the upgrade-px.PIE.

Step 6 After removing the upgrade-px.PIE execute the i nstall commit command to commit the newly activ ated

software

router(admin)# install commit

Step 7 Check to see if there were any failed startup configurations. If there were any startup configurations that

failed (were not applied), then refer to the Caveats section to see how it should be handled.

router# show config failed startup

In same very rare cases inconsistencies in the content of the internal configuration files can occur. In
order to avoid such situations, the following steps are recommended before activating packages:

Step 8 Clear the NVGEN cache:

router# run nvgen -F 1

Step 9 Create a dummy config commit:

router# config
router(config)#hostname <hostname>
router(config)#commit
router(config)#end

Step 10 Force commit update by using the reload command. Press n when the confirmation prompt appears:

router# reload
Updating Commit Database. Please wait...[OK]
Proceed with reload? [confirm] <- Press "n"

In same cases the following error may be reported:

router#reload

Preparing system for backup. This may take a few minutes ............System

configuration backup in progress [Retry later]

In such a case please re-try the command after some time.

Post-Upgrade Procedure

Step 1 Restore the IGP metric if it had been changed before the upgrade

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-16

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

OSPF

router(config-ospf)#no max-metric router-lsa

ISIS

router(config-isis)#no set-overload-bit

Disk Cleanup (Optional)

Once the software upgrade or downgrade has been completed, you can recover some disk space by
removing any inactive packages that are no longer needed (if the packages are required at a later time,
they can be re-added):

Step 1 Obtain the list of inactive packages and note the names of packages that are not needed:

router(admin)# show install inactive brief

Step 2 Remove the unnecessary inactive packages:

router(admin)# install remove disk0:<package_name1> disk0:<package_name2> ..
disk0:<pkg_nameN> sync

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

or

router(admin)# install remove inactive(to remove all inactive packages)

Using the sync option prevents other users from executing any other command during the install
operation.

Step 3 Verify/fix the configuration file system (mandatory)

router(admin)#cfs check

Step 4 If the max-metric or set ove rlo a d bi t was set during any of the pre-upgrade tasks restore the metric

using the following commands:

OSPF

router(config-ospf)#no max-metric router-lsa

ISIS

router(config-isis)#no set-overload-bit

Upgrade Firmware (Mandatory)

Both the ROMMON and the FPGA firmw are need to be upgraded af ter the <v ersion> image installation
on the system. For detailed upgrade procedure please refer to the IOS XR Firmware Upgrade Guide
document which can be accessed at:

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

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-17

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Also refer to the “Other Firmware Support" section in the Release Notes for Cisco CRS-1 and Cisco
CRS-3 for Cisco IOS XR Software Release 4.0.2 document which can be accessed at:

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.0/general/release/notes/reln_402crs.html

Caveats:

During software upgrade or downg rade, the system could detect incompatible configur ation and remo ve
it from the running configuration. The removed configuration will be saved to a file on the router. A
configuration could also fail due to syntax or semantic error as the router boots the new version of the
software.

To resolve these issues, you must browse the removed or failed configuration and then address the
changes so that the configuration can be properly applied on the new version of software.

Addressing Incompatible and Removed Configurations

During the test activation of a new software version, incompatible configurations will be identified and
removed from the router running configuration. Syslog and console logs will provide the necessary
information on the name of the removed configuration file. To address the incompatible configuration,
you should browse the remov ed conf iguration f i le, address the syntax and semantics errors and re-app ly
the config as required and/or applicable after upgrade.

To display the removed configuration, execute the following command from exec mode:

router# show configuration removed <removed config filename>

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Addressing Failed Admin and Non-Admin Configurations During Reload

Some configuration may fail to take effect when the router boots with the new software. These
configurations will be sav ed as failed conf iguratio ns. During acti vation o f the new sof tware versio n, you
will be notified via syslog and console log if a configuration failed to take effect. To address the failed
configuration, you should browse both the admin and non-admin failed configurations, address any
syntax and semantics errors found, and then re-apply it as required.

To display the failed configuration, execute the following commands:

router# show configuration failed startup
router(admin)# show configuration failed startup

MDR - Minimum Disruption Restart

The MDR (Minimum Disruption Restart) feature is not supported for upgrades to the
Cisco

IOS XR software 4.0.0.T, Cisco IOS XR software 4.0.1, or Cisco IOS XR software 4.0.2 releases.

Limitations With the Preconfig Interface

It is important that you check to see whether the persistent config and the running config are the same
or different. If they are different then it will ha ve a problem af ter reload/upgrade, because reload/upgrade
will use the persistent config to restore configuration and the restored configuration will be different
from the one you were running.

Execute the following commands to verify that the persistent conf ig and the runnin g config are the same:

show cfgmgr persistent-config - shows the persistent config in CLI form
show running-config - shows running config

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-18

OL-13669-03

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

You should not use the no interface preconfig <> command if you find that the same config exists in
both preconfig and activate. Use the cfs check command to resolve the inconsistency.

Upgrade Instructions for FAT32

Step 1 Once the system is up and running with FAT32, please check the disk usage on the router and make sure

at least 1.3 GB is free on the Cisco
shouldn't be taking more than 600 MB)

a. Please make sure all inactive old Cisco IOS XR software rele ase pack ages (older than

Cisco

IOS XR software release 4.0.0.T) are removed from the disk.

b. Please make sure all dumper core files and any user files like PIEs etc. are removed from the boot

device to save space.

Step 2 Make sure system (RP) has available memory. Please refer to the table above with title RP/SP/LC

Memory Requirements during Upgrade.

Step 3 Make sure other management nodes RP/DRP/SC also have available memory. This is applicable to a

multishelf platform. The available memory on other RPs should be around the same as the Standby RP
of the DSC.

Step 4 Copy the TAR ball of all Cisco IOS XR software release 4.0 PX packages (mini-px.pie + upgrade

package + optional PX Package and any SMUs) to the hard disk.

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

CRS router (We don't need 1.3 GB for the upgrade, but 4.0.0.T

Warning

Note The Upgrade Package is absolutely necessary in order to upgrade from a pre 4.0 PX

DO NOT COPY THIS TAR BALL PACKAGE TO THE BOOT DEVICE WHICH IS TYPICALLY DISK 0:.

Cisco IOS XR software release to the 4.0 PX Cisco IOS XR software release

Note Make sure all mini and optional packages/SMUs are PX. Do not mix and match packages/SMUs.

Warning

Make sure the T AR pa ckag e contains all the necessary optional packages (mgbl, mpls, mcast, k9sec,
doc, diag, fpd). If any of the packages are missed during the upgrade, upgrade activation doesn't
complain about the missing package and incompatibilities.

If install add is being done as TAR ball, then the memory requirements on the Route Processor (RP)
would be high as contents would be untarred in the /tmp folder. To avoid the usage of RP memory, you
can resort to install add of independent packages using the below command. But this typically leads to
longer install add times than with the TAR ball install add.

install add source harddisk: pie1 pie2 pie3…..

Step 5 Once the router comes back up with new software, please perform your stability checks and then do the

below operations to unblock further install operations.

a. Install the Deactivate Upgrade Package

OL-13669-03

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-19

Chapter 1 Migrating to a Cisco CRS-3 Carrier Routing System

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

b. Install the Remove Upgrade Package: This operation removes the dummy packages of

Cisco

IOS XR software release 4.0; no Cisco IOS XR software release 4.0 software is being
removed. This is only a bridging package to facilitate upgrade fr om Cisco
pre-4.0 software to Cisco
changed. The upgrade package contains Cisco
compatible with Cisco
you have upgraded to Cisco
Cisco

IOS XR software release 4.0 has completed successfully, the Cisco IOS XR software release

4.0 dummy packages (which were installed solely for compatibility with the existing
Cisco

IOS XR software release pre-4.0 packages) can be removed safely.

Step 6 Now perform an install commit command and continue testing the Cisco IOS XR software release

4.0.0.T.PX Image.

IOS XR software release 4.0 software as the package names have

IOS XR software release 4.0 dummy packages

IOS XR software release pre-4.0 packages which are not typically used once

IOS XR software release 4.0 software. Once your upgrade to

IOS XR software release

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing
System Hardware Compatibility Matrix

To convert the existing 40G based Cisco CRS-1 system to 140G based Cisco CRS-3 system, the MSC,
PLIM & Fabric cards would need to be replaced.

Refer to Table 1-5 on page 1-20 for the new 140G-based Cisco CRS-3 hardware.

Tab le 1-5 140G-based Cisco CRS-3 Hardware

Existing
Chassis CRS-3 MSC CRS-3 PLIM Note

SC : 16 slot MSC-140G

FP-140G

8 slot chassis MSC-140G

FP-140G

4 slot chassis MSC-140G

FP-140G

MC : 16 slot LCC MSC-140G

FP-140G

14x10GE
20x10GE
1x100GE
14x10GE
20x10GE
1x100GE
14x10GE
20x10GE
1x100GE
14x10GE
20x10GE

Current CRS-1

Current CRS-1

MSC-140 must NOT be plugged
in with CRS-1 Fabric

Current CRS-1

MC : 16 slot FCC N/A N/A CRS-FCC-FC140/M (S2)

Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide

1-20

1x100GE

[8 planes | 1 plane/board]
[8 planes | 1 plane/ 3 boards for

Multimodule config]

OL-13669-03